- Limit changes query plan
- [mike.aubury@aubit.com: PGconn ?]
- ONLINE TRAINING FOR SAP AND NET WEAVER
- [Fwd: [COMMITTERS] pgsql: Stamp 8.3 in CVS.]
- <IDLE> and waiting
- Re: timestamp format bug
- Re: BUG: type of "xxxx" does not match that when preparing the plan
- timestamp format bug
- Re: Oops - BF:Mastodon just died
- Re: {**Spam**} Re: [PATCHES] Proposed patch:synchronized_scanning GUC variable
- Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
- Re: [PATCHES] Better default_statistics_target
- Re: Will PostgreSQL get ported to CUDA?
- Re: [PATCHES] Proposed patch: synchronized_scanningGUC variable
- Re: Oops - BF:Mastodon just died
- Re: [PATCHES] Better default_statistics_target
- Re: [GENERAL] Errors with run_build.pl - 8.3RC2
- [PATCH] Add TimeOffset and DateOffset typedefs
- Fixed patch for timestamp refactor effort
- [PATCH] Add TimeOffset and DateOffset typedefs
- Re: autonomous transactions
- Re: Suboptimal plan choice problem with 8.3RC2
- Re: [LIKELY_SPAM]Thoughts about bug #3883
- autonomous transactions
- find_typedef alternative that works on mainstream systems
- Makefile support for Mac OS X Fat Binaries?
- Thoughts about bug #3883
- Strange locking choices in pg_shdepend.c
- benchmark farm
- Polyphase Merge
- Rabbit Jewelry: A Sign Of Refinement
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce
- mklink of pg_standby
- Anyone tried PG with Perl 5.10?
- Bug in psql/enum
- Re: [GENERAL] setof record "out" syntax and returning records
- Minor bug in src/port/rint.c
- select statement details
- Re: [GENERAL] SHA1 on postgres 8.3
- message string fixes
- [PATCH] Add size/acl information when listing databases
- SHM_HUGETLB on Linux 2.6.
- sun to buy mysql
- Traveling to London
- Recent pg_regress changes break testing under SELinux
- =?UTF-8?Q?Problem_with_correct_compiling_and_linking__se rver_side?==?UTF-8?Q?_C_function_on_Windows_,c++_Builder___?=
- username &password
- proposal: generic function, constructor function
- Re: modularity of PostgreSQL
- Re: modularity of PostgreSQL
- modularity of PostgreSQL
- Re: Simple thing to make pg_autovacuum more useful
- Re: Simple thing to make pg_autovacuum more useful
- Re: proposal for 8.4: PL/pgSQL - statement CASE
- proposal for 8.4: PL/pgSQL - statement CASE
- Renaming a constraint's index
- Re: VACUUM FULL out of memory
- Re: Password policy
- postgresql in FreeBSD jails: proposal
- Thick indexes - a look at count(1) query
- WAL logging of hash indexes
- COPY encoding
- Password policy
- Re: [COMMITTERS] pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY
- ts_headline() dumps core
- Array behavior oddities
- Re: to_char incompatibility
- Re: [COMMITTERS] pgsql: Most recent Postgres version is 8.2.6, perreport from Robert
- Re: Postgresql Materialized views
- Pl/Java broken since Postgresql 8.3-rc1
- Re: Postgresql Materialized views
- Using tapes on tuplesort.c
- Distinguishing autovacuum activity in pg_stat_activity
- Unexpected log chatter during transaction abort in CVS HEAD
- Make pg_dump suppress COMMENT ON SCHEMA public ?
- Re: timestamp refactor effort
- getting out boolean value from PQgetValue function
- Postgresql Materialized views
- A note about SIGTERM illusion and reality
- DECLARE CURSOR code question
- Declarative partitioning grammar
- proposed libpq type system changes 0.9
- could not open relation: Invalid argument
- Transaction Snapshot Cloning
- scan.l: check_escape_warning()
- Storage Model for Partitioning
- Pl/Java broken since Postgresql 8.3-rc1
- Re: to_char incompatibility
- tag REL8_2_6 not present in file xyz
- Re: to_char incompatibility
- to_char incompatibility
- Re: to_char incompatibility
- flex/bison output wrongly created in the source directory
- odd convert_from bug
- tzdata issue on cross-compiled postgresql
- LD_LIBRARY_PATH not honored on Debian unstable
- operator suggest " interval / interval = numeric"
- Some ideas about Vacuum
- Some notes about the index-functions security vulnerability
- Problem with CVS HEAD's handling of mergejoins
- Named vs Unnamed Partitions
- Re: Psql command-line completion bug
- Proposal - libpq Type System beta-0.8a (was PGparam)
- Psql command-line completion bug
- Data from zone.tab
- Re: 8.3.0 release schedule (Was:Re: [BUGS] BUG
- 8.3.0 release schedule (Was:Re: [BUGS] BUG #3852: Couldnot create complex aggregate)
- ERROR: translation failed from server encoding to wchar_t
- Re: Bug: Unreferenced temp tables disables vacuumto update xid
- Re: Index trouble with 8.3b4
- Re: Bug: Unreferenced temp tables disables vacuum to updatexid
- Random plan selection in DBT-3
- beta4 accepts foreign key of different type than column
- Re: Bug: Unreferenced temp tables disables vacuum to updatexid
- pg 8.3 Windows installer suggestion
- Away until Wed 9 Jan
- [PATCH] pg_hba.conf.sample: mention www.postgresql.org
- Re: Problem with PgTcl auditing function on trigger
- Re: Problem with PgTcl auditing function on trigger
- OUTER JOIN performance regression remains in 8.3beta4
- SSL over Unix-domain sockets
- timestamp typedefs
- Tuning Postgresql on Windows XP Pro 32 bit
- (NONE)
- Slow count(*)
- Index performance
- Dynamic Partitioning using Segment Visibility Maps
- Autovacuum & Table List Ordering
- Table rewrites vs. pending AFTER triggers
- concurrency in psql
- 8.3RC1 release date
- Index Page Split logging
- M.I,5-Persec ution ` MI 5 Insis t th at the se Fax es m ust Contin ue
- M,I.5'Persecu tion 2 2,544 + 83 7 = 2 3,381
- hack
- M`I'5.Perse cution ` M I5 Wan t Me to Send Yo u th ese Fa xes
- M.I'5`P ersecution ` Three Y ears of M I5 Pe rsecution F axes
- M'I-5'Persecut ion Harassm ent thr ough th e Radi o
- M-I,5.Persec ution - No Jus tice f or t he Vict ims of MI 5
- M`I 5.Pers ecution . M I5 Hav e Systematical ly Des troyed My Li fe
- M I`5'Persecut ion MI5 are A fraid to A dmit Theyr e Behi nd t he Perse cution
- question about timestamp
- M.I 5.Pe rsecution ` Molest ation d uring Tr avel
- Selectivity estimation for equality and range queries
- Archiver behavior at shutdown
- Unworkable column delimiter characters for COPY
- M'I.5,Per secution BB C Newscast ers Li e & Deny The yre Wa tching Me
- M`I,5.Persecution - Fo ur Years of M I5 Pe rsecution Po sts on Int ernet Newsgr oups
- M`I,5.Persec ution ` M I5 W aste Ta xpayer Million s on Pointl ess Hate-Campa ign
- M I.5,Persecution Compar ing th e M I5 P ersecution wit h Ge rman Fi nal Soluti on
- Binary data type with other output method
- Why "date" is not a keyword, and is not processed as other buildin types in format_type?
- Re: Spoofing as the postmaster
- viewing source code
- Re: Spoofing as the postmaster
- Spoofing as the postmaster
- binary decode
- Re: function body actors (was: [PERFORM] viewing source code)
- Re: New style of hash join proposal
- Re: pgsql: Improve wording.
- timetz range check issue
- Postgres.bki
- function body actors (was: [PERFORM] viewing source code)
- Re: function body actors (was: [PERFORM] viewing source code)
- Problem
- query : max size Bytea
- duplicate columns with COPY
- PGCon 2008 - call for papers
- Re: Testing mail list
- Benchmark for GiST index?
- autoconf trouble in the CVS HEAD
- binary array and record recv
- Should pg_dump warn on external file dependencies?
- V8.3.0: PQprepare()/PQexecPrepared() and DECLARE CURSOR
- Re: pgsql: Improve wording.
- Board for developers
- Re: Board for developers
- ecxt_scantuple has wrong TupleDesc
- Requesting clarification on Vacuuming/Freezing behaviour
- Proposal for Null Bitmap Optimization(for Trailing NULLs)
- idea for 8.4. using partitioning for temporary tables?
- stored procedures to webservices
- [postgres@microbizz.nl: Getting multiple values from asequence?generator]
- EXPLAIN ANALYZE printing logical and hardware I/O per-node
- standalone hot backup docs
- Negative LIMIT and OFFSET?
- Re: [GENERAL] Slow PITR restore
- New style of hash join proposal
- [Fwd: [PATCHES] archiver ps display]
- Re: [GENERAL] Slow PITR restore
- Re: Current code for function j2date does not have the same correct dynamic range as older code.
- Recreating archive_status
- Trigger problem - conclusion
- test
- foreign keys
- ScalarArrayOp advancing array keys
- little correction
- [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]
- 8.3beta4 space reduction
- psql \dFp's behavior
- Why my C function is called twice?
- Re: PGparam proposal
- Re: Document how to turn off disk write cache on popularoperating
- Re: partitioned table query question
- WORM and Read Only Tables (v0.1)
- VLDB Features
- VACUUM ANALYZE out of memory
- Re: Release Note Changes
- PGparam proposal
- Re: Release Note Changes
- Re: Release Note Changes
- Trigger proglem
- archive_command failures report confusing exit status
- pg_dump roles support
- O(n^2) aggregates
- Problem of a server gettext message.
- Re: Release Note Changes
- Re: Release Note Changes
- whats the deal with -u ?
- PGparam timestamp question
- Bad security practice in oid2name and pgbench
- Re: buildenv.pl/buildenv.bat
- Re: buildenv.pl/buildenv.bat
- Re: [DOCS] "distributed checkpoint"
- pg_controldata doesn't report 64/32bit?
- Re: [DOCS] "distributed checkpoint"
- Possible PostgreSQL 8.3beta4 bug with MD5 authentication in psql?
- Re: Problem with ControlFileData structure being ABI depe ndent
- pgindent issue with EXEC_BACKEND-only typedefs
- Going to Japan
- pg_dump and BINARY mode COPY
- Problem with ControlFileData structure being ABI dependent
- Error while sending request to database
- Uniform policy for author credits in contrib module documentation?
- Needs advice on error detection
- shared_buffers, wal_buffers, WAL files, data files
- autoconf
- sell sneakers www.24hoursneakers.com
- sell accept paypal www.24hoursneakers.com
- TOASTed size
- weird - invalid string enlargement request size
- psql's describe command (for sequences) output improvement
- Is postgres.gif missing in cvs?
- Kludge in pg_standby.c
- Integer datatimes vs msvc
- 8.3 beta 4 crash on windows 2003 64-bit
- Propose removing contrib/spi/preprocessor/
- Re: [COMMITTERS] pgsql: Improve the manual's discussion of partitioning.
- buildenv.pl/buildenv.bat
- Re: [GENERAL] Stored procedure issue