Mailing lists [pgsql-hackers]

1 February 2008

• 00:51   and waiting Gurjeet Singh
• 00:58   Re: timestamp format bug Roberts, Jon
• 03:20   Re: [PATCHES] Better default_statistics_target Robert Treat
• 04:44   [Fwd: [COMMITTERS] pgsql: Stamp 8.3 in CVS.] Devrim GÜNDÜZ
• 07:03   [mike.aubury@aubit.com: PGconn ?] Michael Meskes
• 07:14   Re: [mike.aubury@aubit.com: PGconn ?] Tom Lane
• 10:08   Limit changes query plan Gaetano Mendola
• 10:16   Re: Limit changes query plan Martijn van Oosterhout
• 10:43   Re: Limit changes query plan Gaetano Mendola
• 11:35   Re: Limit changes query plan Gregory Stark
• 13:22   Re: Limit changes query plan Gaetano Mendola
• 14:18   Re: [PATCHES] Better default_statistics_target Kevin Grittner
• 14:48   Re: Limit changes query plan Tom Lane
• 14:50   Re: [PATCHES] Better default_statistics_target Tom Lane
• 14:52   FW: bitemporal functionality for PostgreSQL Luke Porter
• 15:02   Re: FW: bitemporal functionality for PostgreSQL Tom Lane
• 15:07   Re: Limit changes query plan Greg Stark
• 15:15   Re: FW: bitemporal functionality for PostgreSQL A.M.
• 15:16   Re: and waiting Tom Lane
• 15:20   Re: Limit changes query plan Tom Lane
• 16:18   Re: Limit changes query plan Gaetano Mendola
• 17:09   Re: FW: bitemporal functionality for PostgreSQL Jeff Davis
• 17:26   Backward reading 
• 19:34   Re: Backward reading Simon Riggs
• 20:25   Re: [BUGS] BUG #3921: CREATE TABLE / INCLUDING INDEXES fails with permission denied Tom Lane
• 20:32   Re: Backward reading Gregory Stark
• 21:16   Re: BUG #3921: CREATE TABLE / INCLUDING INDEXES fails with permission denied Gregory Stark
• 21:26   Re: and waiting Gurjeet Singh
• 21:33   configurability of OOM killer Alvaro Herrera
• 21:48   Re: Backward reading 
• 22:57   Re: and waiting Tom Lane
• 23:08   Re: configurability of OOM killer Tom Lane
• 23:37   Re: configurability of OOM killer Andrew Dunstan
• 23:49   Re: and waiting Gurjeet Singh

2 February 2008

• 03:17   Re: Truncate Triggers Decibel!
• 10:27   Strange behavior on plpgsql trigger function in if comparison Omar Bettin
• 10:49   Re: Strange behavior on plpgsql trigger function in if comparison Stefan Kaltenbrunner
• 11:55   Re: BK-Tree Implementation on top of GiST Volkan Yazıcı
• 12:18   Problem with site doc search Gurjeet Singh
• 12:41   Re: Strange behavior on plpgsql trigger function in if comparison Andrew Dunstan
• 15:22   Re: configurability of OOM killer Florian Weimer
• 16:24   Run positions on Tape 
• 16:40   Re: configurability of OOM killer Tom Lane
• 17:15   Re: configurability of OOM killer Florian Weimer
• 17:43   Re: Truncate Triggers David Fetter
• 18:17   Re: configurability of OOM killer Tom Lane
• 18:25   Re: Truncate Triggers Tom Lane
• 18:25   Re: configurability of OOM killer Florian G. Pflug
• 18:40   Re: configurability of OOM killer Florian Weimer
• 18:43   Re: Truncate Triggers David Fetter
• 19:01   Re: configurability of OOM killer Andrew Dunstan
• 19:17   Re: configurability of OOM killer Tom Lane
• 19:49   Re: configurability of OOM killer Florian G. Pflug
• 20:23   clone varlena function Pavel Stehule
• 20:37   Re: configurability of OOM killer Dimitri Fontaine
• 20:54   Re: clone varlena function Tom Lane
• 21:05   Re: clone varlena function Pavel Stehule
• 21:08   Re: Problem with site doc search Oleg Bartunov
• 21:23   Re: Truncate Triggers Christopher Browne
• 21:26   Re: Truncate Triggers David Fetter
• 21:28   Re: and waiting Tom Lane
• 21:38   Re: Truncate Triggers Tom Lane
• 22:14   Re: and waiting Gurjeet Singh
• 22:28   Re: and waiting Alvaro Herrera
• 22:34   Re: and waiting Gurjeet Singh
• 22:39   Re: and waiting Tom Lane

3 February 2008

• 04:05   Wrong query examples in docs Gurjeet Singh
• 04:14   Re: Wrong query examples in docs Tom Lane
• 04:14   Re: Wrong query examples in docs Gurjeet Singh
• 04:49   Re: RFC: array_agg() per SQL:200n Neil Conway
• 09:48   Re: FW: bitemporal functionality for PostgreSQL Heikki Linnakangas
• 10:56   Re: configurability of OOM killer Martijn van Oosterhout
• 12:16   Re: configurability of OOM killer Andrew Dunstan
• 12:26   Re: configurability of OOM killer Gregory Stark
• 12:49   Re: Truncate Triggers Simon Riggs
• 14:56   Re: configurability of OOM killer Tom Lane
• 14:58   Autoconf 2.61 Peter Eisentraut
• 15:39   Re: Problem with site doc search Magnus Hagander
• 18:31   Re: FW: bitemporal functionality for PostgreSQL Jeff Davis
• 19:56   Re: FW: bitemporal functionality for PostgreSQL Greg Smith
• 23:27   NULL OR ZERO Omar Bettin
• 23:41   Re: NULL OR ZERO Jaime Casanova

4 February 2008

• 02:13   Reverse key index Gurjeet Singh
• 02:44   Re: Truncate Triggers Greg Sabino Mullane
• 02:45   Reg: Question about concurrency/locking rkalyankumar@aol.in
• 03:02   Re: [PATCHES] Better default_statistics_target Greg Sabino Mullane
• 03:38   Re: Reg: Question about concurrency/locking Tom Lane
• 07:56   Merge condition in postgresql Amit jain
• 09:09   Re: FW: bitemporal functionality for PostgreSQL Dimitri Fontaine
• 09:20   Re: configurability of OOM killer Simon Riggs
• 10:16   Re: NULL OR ZERO Andrei Kovalevski
• 12:35   Re: Reverse key index Kenneth Marshall
• 13:00   Re: configurability of OOM killer Ron Mayer
• 13:27   Re: Merge condition in postgresql Stephen Frost
• 14:46   Re: Merge condition in postgresql Roberts, Jon
• 15:06   Page-at-a-time Locking Considerations Simon Riggs
• 15:10   Re: Merge condition in postgresql Martijn van Oosterhout
• 16:36   release checklist Andrew Dunstan
• 17:20   Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Tom Lane
• 17:27   Re: Page-at-a-time Locking Considerations Tom Lane
• 17:44   Re: Page-at-a-time Locking Considerations Simon Riggs
• 17:46   Why are we waiting? Simon Riggs
• 17:47   Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Andrew Dunstan
• 17:57   Re: configurability of OOM killer Jeff Davis
• 18:24   Re: release checklist Tom Lane
• 18:29   Re: configurability of OOM killer Simon Riggs
• 18:39   Re: configurability of OOM killer Jeff Davis
• 18:44   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Tom Lane
• 18:54   Re: FW: bitemporal functionality for PostgreSQL Jeff Davis
• 19:03   Re: Page-at-a-time Locking Considerations Gregory Stark
• 19:07   Re: configurability of OOM killer Simon Riggs
• 19:31   Re: configurability of OOM killer Tom Lane
• 19:41   Re: configurability of OOM killer Alvaro Herrera
• 19:44   Re: Page-at-a-time Locking Considerations Alvaro Herrera
• 19:46   Re: configurability of OOM killer Simon Riggs
• 19:50   Re: FW: bitemporal functionality for PostgreSQL Heikki Linnakangas
• 19:53   Re: Page-at-a-time Locking Considerations Simon Riggs
• 20:05   Re: Page-at-a-time Locking Considerations Tom Lane
• 20:08   Re: Page-at-a-time Locking Considerations Alvaro Herrera
• 20:10   Re: Page-at-a-time Locking Considerations Heikki Linnakangas
• 20:10   Re: Page-at-a-time Locking Considerations Alvaro Herrera
• 20:30   Re: FW: bitemporal functionality for PostgreSQL 0123 zyxw
• 20:32   Re: configurability of OOM killer Ron Mayer
• 20:41   Re: configurability of OOM killer Jeff Davis
• 20:48   Re: configurability of OOM killer Tom Lane
• 20:53   Re: configurability of OOM killer Jeff Davis
• 20:59   Re: configurability of OOM killer Simon Riggs
• 21:01   Re: configurability of OOM killer Jeff Davis
• 21:06   Re: Why are we waiting? Tom Lane
• 21:16   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Peter Eisentraut
• 21:25   Re: FW: bitemporal functionality for PostgreSQL Jeff Davis
• 22:48   TODO item:Allow to_date() and to_timestamp() accept localized month names Gevik Babakhani
• 23:21   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Tom Lane

5 February 2008

• 00:14   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Gevik Babakhani
• 00:28   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Andrew Dunstan
• 00:29   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Tom Lane
• 00:37   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Tom Lane
• 00:59   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Alvaro Herrera
• 01:10   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Tom Lane
• 01:55   Re: Problem with site doc search Gurjeet Singh
• 05:45   Amit jain wants to chat Amit jain
• 05:46   Amit jain wants to chat Amit jain
• 07:04   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Peter Eisentraut
• 07:25   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Gevik Babakhani
• 09:10   Re: Why are we waiting? Simon Riggs
• 09:13   Re: Page-at-a-time Locking Considerations Simon Riggs
• 09:24   path with spaces in config.pl Gevik Babakhani
• 09:29   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Magnus Hagander
• 09:57   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Dave Page
• 10:06   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Magnus Hagander
• 10:09   Re: path with spaces in config.pl Magnus Hagander
• 10:50   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Andrew Dunstan
• 11:00   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Dave Page
• 11:35   Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Gregory Stark
• 11:49   Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Andrew Dunstan
• 11:56   Re: path with spaces in config.pl Gevik Babakhani
• 12:46   Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Gregory Stark
• 13:15   Re: Why are we waiting? Heikki Linnakangas
• 13:17   Re: path with spaces in config.pl Magnus Hagander
• 13:25   patternsel() and histogram_selectivity() and the hard cutoff of 100 Gregory Stark
• 13:56   Re: Why are we waiting? Simon Riggs
• 14:27   Re: [BUGS] BUG #3909: src\tools\msvc\clean.bat clears parse.h file Magnus Hagander
• 14:31   Re: GSSAPI and V2 protocol Magnus Hagander
• 14:36   Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) Magnus Hagander
• 15:09   Re: Problem with site doc search Magnus Hagander
• 15:19   Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) Dave Page
• 15:24   Re: [BUGS] BUG #3909: src\tools\msvc\clean.bat clears parse.h file Dave Page
• 15:35   Re: patternsel() and histogram_selectivity() and the hard cutoff of 100 Gregory Stark
• 15:55   Re: Why are we waiting? Tom Lane
• 16:55   Re: [BUGS] BUG #3909: src\tools\msvc\clean.bat clears parse.h file Magnus Hagander
• 17:06   Re: GSSAPI and V2 protocol Kris Jurka
• 17:10   Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) Magnus Hagander
• 17:12   Re: GSSAPI and V2 protocol Magnus Hagander
• 17:44   Re: GSSAPI and V2 protocol Kris Jurka
• 17:49   Re: GSSAPI and V2 protocol Magnus Hagander
• 18:32   Possible BUG in MSVC Install.pm in GenerateNLSFiles Gevik Babakhani
• 18:46   Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) Dave Page
• 19:03   Re: Possible BUG in MSVC Install.pm in GenerateNLSFiles Andrew Dunstan
• 19:16   Re: Possible BUG in MSVC Install.pm in GenerateNLSFiles Gevik Babakhani
• 19:57   Feature Freeze Date for Next Release Simon Riggs
• 20:04   Re: Feature Freeze Date for Next Release Dave Page
• 20:12   Re: Feature Freeze Date for Next Release Ron Mayer
• 20:33   Re: configurability of OOM killer Decibel!
• 20:47   Re: [BUGS] BUG #3909: src\tools\msvc\clean.bat clears parse.h file Dave Page
• 20:54   Re: configurability of OOM killer Ron Mayer
• 20:56   Re: Feature Freeze Date for Next Release Ron Mayer
• 21:03   Re: Feature Freeze Date for Next Release Joshua D. Drake
• 21:46   Re: Feature Freeze Date for Next Release Tom Lane
• 23:41   Where is share\locale dir on Win? Gevik Babakhani
• 23:42   Re: GSSAPI and V2 protocol Tom Lane

6 February 2008

• 00:40   Re: configurability of OOM killer Decibel!
• 02:55   Re: GSSAPI and V2 protocol Tom Lane
• 03:31   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Marc G. Fournier
• 06:57   Re: GSSAPI and V2 protocol Kris Jurka
• 07:24   Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59 Peter Eisentraut
• 07:56   PostgreSQL 8.4 development plan Dave Page
• 10:32   Re: GSSAPI and V2 protocol Magnus Hagander
• 11:00   Re: PostgreSQL 8.4 development plan Simon Riggs
• 12:00   Re: [BUGS] BUG #3909: src\tools\msvc\clean.bat clears parse.h file Magnus Hagander
• 12:49   Re: PostgreSQL 8.4 development plan Magnus Hagander
• 13:24   HeapTupleSatisfies micro tuning Simon Riggs
• 13:31   Re: Why are we waiting? Staale Smedseng
• 13:42   Re: PostgreSQL 8.4 development plan Dave Page
• 13:44   Re: PostgreSQL 8.4 development plan Magnus Hagander
• 13:48   Re: Why are we waiting? Simon Riggs
• 13:49   Re: PostgreSQL 8.4 development plan Dave Page
• 13:56   Re: Why are we waiting? Gregory Stark
• 14:12   pg_dump additional options for performance Simon Riggs
• 14:13   Re: [BUGS] BUG #3909: src\tools\msvc\clean.bat clears parse.h file Magnus Hagander
• 14:48   Segment Visibility Map for VACUUM Simon Riggs
• 14:48   Re: pg_dump additional options for performance Andrew Dunstan
• 14:55   Re: pg_dump additional options for performance Simon Riggs
• 15:01   Re: PostgreSQL 8.4 development plan Andrew Dunstan
• 15:10   Re: pg_dump additional options for performance Zeugswetter Andreas ADI SD
• 15:13   Re: PostgreSQL 8.4 development plan Peter Eisentraut
• 15:14   Re: PostgreSQL 8.4 development plan Dave Page
• 15:14   Re: pg_dump additional options for performance Magnus Hagander
• 15:23   Re: PostgreSQL 8.4 development plan Brendan Jurd
• 15:27   Re: PostgreSQL 8.4 development plan Andrew Dunstan
• 15:32   Re: pg_dump additional options for performance Richard Huxton
• 15:36   Re: PostgreSQL 8.4 development plan Dave Page
• 15:49   Re: PostgreSQL 8.4 development plan Andrew Dunstan
• 15:57   Re: Page-at-a-time Locking Considerations Zdenek Kotala
• 16:04   Re: PostgreSQL 8.4 development plan Tom Lane
• 16:09   Re: PostgreSQL 8.4 development plan Tom Lane
• 16:13   Re: PostgreSQL 8.4 development plan Andrew Dunstan
• 16:19   build environment: a different makefile Paul van den Bogaard
• 16:23   Re: PostgreSQL 8.4 development plan Tom Lane
• 16:29   Re: Page-at-a-time Locking Considerations Tom Lane
• 16:45   Re: Why are we waiting? Staale Smedseng
• 17:03   Re: Why are we waiting? Simon Riggs
• 17:12   Re: PostgreSQL 8.4 development plan Josh Berkus
• 17:35   Re: Why are we waiting? Staale Smedseng
• 17:38   Re: GSSAPI and V2 protocol Tom Lane
• 17:44   Re: PostgreSQL 8.4 development plan Gevik Babakhani
• 17:46   crash / data recovery issues Robert Treat
• 17:52   Re: PostgreSQL 8.4 development plan Alvaro Herrera
• 17:56   Re: Why are we waiting? Tom Lane
• 17:58   Re: crash / data recovery issues Alvaro Herrera
• 18:20   Re: Why are we waiting? Simon Riggs
• 18:31   Re: crash / data recovery issues Tom Lane
• 18:33   Re: crash / data recovery issues Robert Treat
• 18:37   Re: Page-at-a-time Locking Considerations Zdenek Kotala
• 18:42   Re: Why are we waiting? Tom Lane
• 18:49   Re: Why are we waiting? Simon Riggs
• 18:56   Re: GSSAPI and V2 protocol Magnus Hagander
• 18:58   Re: Page-at-a-time Locking Considerations Tom Lane
• 19:01   Re: Why are we waiting? Tom Lane
• 19:36   Re: PostgreSQL 8.4 development plan Peter Eisentraut
• 19:41   Re: PostgreSQL 8.4 development plan Guillaume Smet
• 19:46   Re: PostgreSQL 8.4 development plan Tom Lane
• 19:59   Re: PostgreSQL 8.4 development plan Joshua D. Drake
• 20:06   Re: PostgreSQL 8.4 development plan Magnus Hagander
• 20:07   Re: Page-at-a-time Locking Considerations Zdenek Kotala
• 20:08   Re: PostgreSQL 8.4 development plan Dimitri Fontaine
• 20:11   Re: PostgreSQL 8.4 development plan Joshua D. Drake
• 20:29   Re: PostgreSQL 8.4 development plan Stefan Kaltenbrunner
• 20:38   Re: NULL OR ZERO Rodrigo E. De León Plicet
• 21:08   Re: build environment: a different makefile Peter Eisentraut
• 22:02   Re: PostgreSQL 8.4 development plan Greg Smith
• 22:12   Re: build environment: a different makefile Tom Lane
• 22:50   Re: PostgreSQL 8.4 development plan Tom Lane
• 23:01   Re: PostgreSQL 8.4 development plan Joshua D. Drake
• 23:01   Re: Page-at-a-time Locking Considerations Gregory Stark
• 23:59   Re: PostgreSQL 8.4 development plan Tom Lane

7 February 2008

• 00:37   Re: PostgreSQL 8.4 development plan Mark Mielke
• 03:25   Re: PostgreSQL 8.4 development plan Bruce Momjian
• 03:36   Re: Page-at-a-time Locking Considerations Bruce Momjian
• 04:36   Re: patch queue needs update was:(PostgreSQL 8.4 development plan) Jaime Casanova
• 05:52   8.3 / 8.2.6 restore comparison Joshua D. Drake
• 06:12   Re: PostgreSQL 8.4 development plan James Mansion
• 07:09   Re: build environment: a different makefile Dave Page
• 07:15   Re: Page-at-a-time Locking Considerations Gregory Stark
• 07:16   Need help with autovacuuming error. S. Horio
• 07:53   Re: Page-at-a-time Locking Considerations Simon Riggs
• 08:51   Re: build environment: a different makefile Magnus Hagander
• 08:53   Re: Page-at-a-time Locking Considerations Zdenek Kotala
• 09:07   Re: PostgreSQL 8.4 development plan Dimitri Fontaine
• 09:09   Re: build environment: a different makefile Peter Eisentraut
• 09:10   Re: PostgreSQL 8.4 development plan Magnus Hagander
• 09:11   Re: [BUGS] possible bug windows setup Magnus Hagander
• 09:12   Re: build environment: a different makefile Zdenek Kotala
• 09:43   Re: build environment: a different makefile Paul van den Bogaard
• 10:12   Re: [BUGS] possible bug windows setup Andrew Dunstan
• 10:16   Re: [BUGS] possible bug windows setup Magnus Hagander
• 10:25   cvs: 8.3 branch/head Michael Meskes
• 10:31   Re: cvs: 8.3 branch/head Magnus Hagander
• 10:33   Re: [BUGS] possible bug windows setup Andrew Dunstan
• 11:22   Need help with decoding of sql array from WAL files version 7.4.17 Andrey Stoev
• 11:31   Re: PostgreSQL 8.4 development plan Stefan Kaltenbrunner
• 11:48   Re: PostgreSQL 8.4 development plan Andrew Dunstan
• 12:02   Re: PostgreSQL 8.4 development plan Stefan Kaltenbrunner
• 13:33   Re: Need help with autovacuuming error. Alvaro Herrera
• 13:47   Re: 8.3 / 8.2.6 restore comparison Andrew Dunstan
• 14:17   Re: build environment: a different makefile Tom Lane
• 14:30   Re: Why are we waiting? Staale Smedseng
• 14:38   Re: Why are we waiting? Tom Lane
• 14:47   Re: PostgreSQL 8.4 development plan Tom Lane
• 14:55   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 15:11   Re: 8.3 / 8.2.6 restore comparison Stephen Frost
• 15:19   Re: PostgreSQL 8.4 development plan Tom Lane
• 15:22   Re: 8.3 / 8.2.6 restore comparison Andrew Dunstan
• 15:32   PostgreSQL 8.3.0 'unrecognized node type: 1718580065' Vladimir Kokovic
• 15:35   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 15:42   Re: PostgreSQL 8.4 development plan Joshua D. Drake
• 15:49   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 15:54   Re: 8.3 / 8.2.6 restore comparison Greg Smith
• 16:01   Re: PostgreSQL 8.4 development plan Alvaro Herrera
• 16:12   Re: Why are we waiting? Simon Riggs
• 16:34   Re: PostgreSQL 8.4 development plan Joshua D. Drake
• 16:46   Re: PostgreSQL 8.4 development plan Magnus Hagander
• 16:54   Re: PostgreSQL 8.4 development plan Aidan Van Dyk
• 16:56   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 16:57   Re: Why are we waiting? Jignesh K. Shah
• 17:07   Re: Why are we waiting? Staale Smedseng
• 17:07   Re: Problem with site doc search Oleg Bartunov
• 17:10   Re: PostgreSQL 8.4 development plan Stefan Kaltenbrunner
• 17:15   Re: PostgreSQL 8.4 development plan Tom Lane
• 17:25   Re: PostgreSQL 8.4 development plan Mark Mielke
• 17:48   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 17:57   Re: PostgreSQL 8.4 development plan Tom Lane
• 18:22   Re: configurability of OOM killer Dawid Kuroczko
• 18:30   Re: {**Spam**} Re: PostgreSQL 8.4 development plan Dimitri Fontaine
• 18:41   Re: {**Spam**} Re: PostgreSQL 8.4 development plan Stefan Kaltenbrunner
• 18:43   Re: PostgreSQL 8.4 development plan Mark Mielke
• 18:48   Re: PostgreSQL 8.3.0 'unrecognized node type: 1718580065' Zdenek Kotala
• 18:54   Turn on COPY_PARSE_PLAN_TREES in assert-enabled builds? Tom Lane
• 19:54   Re: PostgreSQL 8.4 development plan Peter Eisentraut
• 20:04   Re: PostgreSQL 8.4 development plan Gregory Stark
• 20:21   Re: Why are we waiting? Jignesh K. Shah
• 20:24   Re: PostgreSQL 8.4 development plan Tom Lane
• 20:43   Re: PostgreSQL 8.4 development plan Alvaro Herrera
• 20:45   Re: PostgreSQL 8.4 development plan Greg Smith
• 20:47   Re: PostgreSQL 8.4 development plan Magnus Hagander
• 20:49   Re: PostgreSQL 8.4 development plan Dave Page
• 20:50   Re: PostgreSQL 8.4 development plan Magnus Hagander
• 20:50   Re: PostgreSQL 8.4 development plan Mark Mielke
• 20:56   Re: PostgreSQL 8.4 development plan Fabien COELHO
• 20:57   Re: PostgreSQL 8.4 development plan Stefan Kaltenbrunner
• 21:01   Re: PostgreSQL 8.4 development plan Mark Mielke
• 21:06   Re: PostgreSQL 8.4 development plan Heikki Linnakangas
• 21:25   Re: PostgreSQL 8.4 development plan Mark Mielke
• 21:27   Re: PostgreSQL 8.4 development plan Bruce Momjian
• 21:30   Re: PostgreSQL 8.4 development plan Alvaro Herrera
• 21:45   Re: PostgreSQL 8.4 development plan Gregory Stark
• 21:56   Re: PostgreSQL 8.4 development plan Christopher Browne
• 21:56   Re: Why are we waiting? Gregory Stark
• 21:58   Re: PostgreSQL 8.4 development plan Magnus Hagander
• 22:01   Re: configurability of OOM killer Martijn van Oosterhout
• 22:23   Re: Why are we waiting? Tom Lane
• 22:25   Re: configurability of OOM killer Tom Lane
• 22:33   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Gevik Babakhani
• 22:58   Re: GSSAPI and V2 protocol Tom Lane
• 23:10   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 23:20   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 23:37   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 23:52   Re: PostgreSQL 8.4 development plan Gregory Stark

8 February 2008

• 00:39   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 00:53   Re: 8.3 / 8.2.6 restore comparison Mark Wong
• 01:04   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 01:32   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 01:40   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 01:45   Re: configurability of OOM killer Markus Bertheau
• 02:15   Re: Why are we waiting? Jignesh K. Shah
• 05:40   Re: configurability of OOM killer Simon Riggs
• 05:42   Re: configurability of OOM killer Simon Riggs
• 05:43   Re: configurability of OOM killer Simon Riggs
• 06:08   Re: PostgreSQL 8.4 development plan Zdenek Kotala
• 06:18   Re: PostgreSQL 8.4 development plan Zdenek Kotala
• 07:30   Re: PostgreSQL 8.4 development plan Heikki Linnakangas
• 08:55   Re: GSSAPI and V2 protocol Magnus Hagander
• 08:56   Re: configurability of OOM killer Zeugswetter Andreas ADI SD
• 09:02   Re: PostgreSQL 8.4 development plan Mark Cave-Ayland
• 09:06   Re: configurability of OOM killer Dawid Kuroczko
• 09:36   Re: configurability of OOM killer Martijn van Oosterhout
• 09:39   Re: PostgreSQL 8.4 development plan Markus Bertheau
• 10:30   Re: PostgreSQL 8.4 development plan Peter Eisentraut
• 10:54   Re: PostgreSQL 8.4 development plan Brendan Jurd
• 11:15   Re: PostgreSQL 8.4 development plan Peter Eisentraut
• 11:47   Re: PostgreSQL 8.4 development plan Florian Pflug
• 12:01   Re: PostgreSQL 8.4 development plan Aidan Van Dyk
• 12:13   The question of LOCALE at the time of a regression test. Hiroshi Saito
• 12:22   Re: The question of LOCALE at the time of a regression test. Andrew Dunstan
• 12:35   Re: The question of LOCALE at the time of a regression test. Hiroshi Saito
• 12:39   Re: PostgreSQL 8.4 development plan Alvaro Herrera
• 13:19   Re: PostgreSQL 8.4 development plan Florian Pflug
• 13:32   Patch review Gregory Stark
• 14:02   Re: PostgreSQL 8.4 development plan Aidan Van Dyk
• 14:21   Re: PostgreSQL 8.4 development plan Tino Wildenhain
• 14:22   Re: Patch review Alvaro Herrera
• 14:25   Re: PostgreSQL 8.4 development plan Andrew Dunstan
• 14:33   Re: PostgreSQL 8.4 development plan Joshua D. Drake
• 14:39   Re: PostgreSQL 8.4 development plan Alvaro Herrera
• 14:46   Re: Patch review Magnus Hagander
• 14:57   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Bruce Momjian
• 15:10   Re: The question of LOCALE at the time of a regression test. Tom Lane
• 15:23   Re: The question of LOCALE at the time of a regression test. Hiroshi Saito
• 15:48   Re: The question of LOCALE at the time of a regression test. Jeremy Drake
• 15:53   Re: The question of LOCALE at the time of a regression test. Hiroshi Saito
• 16:09   Re: pg_dump additional options for performance Decibel!
• 16:16   Re: The question of LOCALE at the time of a regression test. Andrew Dunstan
• 16:19   Re: The question of LOCALE at the time of a regression test. Hiroshi Saito
• 16:20   "AS" by the syntax of table reference.(8.4 proposal) Hiroshi Saito
• 16:22   Re: The question of LOCALE at the time of a regression test. Tom Lane
• 16:31   Re: The question of LOCALE at the time of a regression test. Hiroshi Saito
• 16:36   Re: configurability of OOM killer Decibel!
• 17:24   Re: GSSAPI and V2 protocol Tom Lane
• 17:56   Re: "AS" by the syntax of table reference.(8.4 proposal) Tom Lane
• 18:15   Re: "AS" by the syntax of table reference.(8.4 proposal) Hiroshi Saito
• 18:52   Re: "AS" by the syntax of table reference.(8.4 proposal) Hiroshi Saito
• 18:59   Re: configurability of OOM killer Alvaro Herrera
• 19:01   Re: pg_dump additional options for performance Alvaro Herrera
• 20:34   Re: "AS" by the syntax of table reference.(8.4 proposal) Tom Lane
• 21:16   Re: "AS" by the syntax of table reference.(8.4 proposal) Gregory Stark
• 23:16   Re: "AS" by the syntax of table reference.(8.4 proposal) Tom Lane
• 23:54   Re: "AS" by the syntax of table reference.(8.4 proposal) Hiroshi Saito

9 February 2008

• 00:10   Re: "AS" by the syntax of table reference.(8.4 proposal) Hiroshi Saito
• 00:11   Re: "AS" by the syntax of table reference.(8.4 proposal) Andrew Dunstan
• 00:21   Re: "AS" by the syntax of table reference.(8.4 proposal) Hiroshi Saito
• 04:17   Re: Patch review Bruce Momjian
• 06:10   Re: Patch review Tom Lane
• 07:27   Re: PostgreSQL 8.4 development plan Joshua D. Drake
• 09:58   Re: PostgreSQL 8.4 development plan Magnus Hagander
• 10:13   Re: "AS" by the syntax of table reference.(8.4 proposal) Gregory Stark
• 11:52   Re: PostgreSQL 8.4 development plan Andrew Dunstan
• 12:07   Re: PostgreSQL 8.3.0 'unrecognized node type: 1718580065' Vladimir Kokovic
• 12:09   Re: Patch review Magnus Hagander
• 15:25   Re: PostgreSQL 8.4 development plan Alvaro Herrera
• 15:51   quoting bug? Patrick Welche
• 16:12   Re: quoting bug? Brendan Jurd
• 16:27   Re: Patch review Tom Lane
• 16:29   Re: quoting bug? Tom Lane
• 17:26   Re: quoting bug? Patrick Welche
• 17:54   Re: Patch review Stefan Kaltenbrunner
• 18:23   Re: Patch review Gregory Stark
• 18:41   Re: Patch review Stefan Kaltenbrunner
• 19:07   Re: "AS" by the syntax of table reference.(8.4 proposal) Tom Lane
• 19:50   Re: "AS" by the syntax of table reference.(8.4 proposal) Gregory Stark
• 20:24   Re: "AS" by the syntax of table reference.(8.4 proposal) Tom Lane
• 21:15   Re: "AS" by the syntax of table reference.(8.4 proposal) Gregory Stark
• 21:22   Re: PostgreSQL 8.4 development plan Jan Wieck
• 21:26   Re: "AS" by the syntax of table reference.(8.4 proposal) Tom Lane
• 21:44   Re: PostgreSQL 8.4 development plan Brendan Jurd
• 23:40   Re: PostgreSQL 8.4 development plan Greg Smith

10 February 2008

• 02:46   Re: "AS" by the syntax of table reference.(8.4 proposal) Hiroshi Saito
• 02:51   Fwd: PostgreSQL 8.4 development plan Christopher Browne
• 09:51   Re: TODO item:Allow to_date() and to_timestamp() accept localized month names Gevik Babakhani
• 10:35   Patch to update libpqxx's homepage in README Gurjeet Singh
• 18:48   Re: Patch review Stefan Kaltenbrunner

11 February 2008

• 09:22   Re: pg_dump additional options for performance Simon Riggs
• 14:15   Re: pg_dump additional options for performance Alvaro Herrera
• 14:30   Re: pg_dump additional options for performance Andrew Dunstan
• 14:50   Re: pg_dump additional options for performance Andrew Dunstan
• 15:04   Re: pg_dump additional options for performance Simon Riggs
• 15:52   Re: pg_dump additional options for performance Tom Lane
• 16:10   Re: pg_dump additional options for performance Simon Riggs
• 16:13   Re: pg_dump additional options for performance Magnus Hagander
• 16:29   Re: pg_dump additional options for performance Simon Riggs
• 16:39   Re: Truncate Triggers Claudio Rossi
• 16:43   Re: pg_dump additional options for performance Andrew Dunstan
• 16:47   Re: pg_dump additional options for performance Tom Lane
• 16:56   Re: pg_dump additional options for performance Christopher Browne
• 17:40   Avoid scanning on tape Manolo _
• 18:28   Re: Avoid scanning on tape Tom Lane
• 18:42   Re: Avoid scanning on tape Manolo _
• 19:07   Re: pg_dump additional options for performance Jeff Davis
• 19:57   Re: Fwd: PostgreSQL 8.4 development plan Robert Treat
• 20:14   Re: Fwd: PostgreSQL 8.4 development plan Andy Colson
• 20:18   Re: Fwd: PostgreSQL 8.4 development plan Alvaro Herrera
• 20:21   Re: Fwd: PostgreSQL 8.4 development plan Mark Mielke
• 20:38   Re: Fwd: PostgreSQL 8.4 development plan Christopher Browne
• 22:18   Re: Fwd: PostgreSQL 8.4 development plan Andrew Dunstan
• 23:59   Re: Fwd: PostgreSQL 8.4 development plan Robert Treat

12 February 2008

• 01:43   Re: Patch review Decibel!
• 01:46   Re: pg_dump additional options for performance Decibel!
• 03:50   Re: Patch review tomas@tuxteam.de
• 03:58   -U option in psql Jaime Casanova
• 04:04   Re: -U option in psql Tom Lane
• 04:19   use of alias Amit jain
• 04:38   Re: use of alias Brett McBride
• 05:07   Re: use of alias Brendan Jurd
• 07:41   Re: patternsel() and histogram_selectivity() and the hard cutoff of 100 Matteo Beccati
• 09:49   Re: Patch review Bruce Momjian
• 10:13   Re: Patch review Martijn van Oosterhout
• 10:22   Re: Patch review Gregory Stark
• 10:34   Re: Patch review Stefan Kaltenbrunner
• 10:36   Re: Patch review Stefan Kaltenbrunner
• 10:53   NLS on MSVC strikes back! Gevik Babakhani
• 11:11   Re: NLS on MSVC strikes back! Andrew Dunstan
• 11:25   Re: NLS on MSVC strikes back! Gevik Babakhani
• 11:30   Re: NLS on MSVC strikes back! Alvaro Herrera
• 11:32   Re: NLS on MSVC strikes back! Gevik Babakhani
• 11:38   Re: NLS on MSVC strikes back! Alvaro Herrera
• 11:42   Re: NLS on MSVC strikes back! Andrew Dunstan
• 11:47   Re: NLS on MSVC strikes back! Gevik Babakhani
• 12:11   Re: NLS on MSVC strikes back! Alvaro Herrera
• 13:00   Re: NLS on MSVC strikes back! Andrew Dunstan
• 13:43   postmaster in a tight loop Dan Langille
• 13:46   Re: postmaster in a tight loop Alvaro Herrera
• 13:58   Re: NLS on MSVC strikes back! Hiroshi Saito
• 14:02   Re: NLS on MSVC strikes back! Bruce Momjian
• 14:04   Re: postmaster in a tight loop Tom Lane
• 14:09   Re: NLS on MSVC strikes back! Tom Lane
• 14:15   Re: NLS on MSVC strikes back! Alvaro Herrera
• 15:31   Re: NLS on MSVC strikes back! Gevik Babakhani
• 15:45   Re: NLS on MSVC strikes back! Alvaro Herrera
• 15:50   Re: NLS on MSVC strikes back! Dave Page
• 15:55   Re: NLS on MSVC strikes back! Alvaro Herrera
• 15:58   Re: Patch review Joshua D. Drake
• 16:15   Re: Patch review Bruce Momjian
• 16:16   Re: Patch review Andrew Dunstan
• 16:18   Re: Patch review Tom Lane
• 16:23   Re: Patch review Bruce Momjian
• 16:27   Re: NLS on MSVC strikes back! Magnus Hagander
• 16:36   Re: Patch review Bruce Momjian
• 16:51   Re: Patch review Bruce Momjian
• 16:58   Re: NLS on MSVC strikes back! Gevik Babakhani
• 22:45   Re: Patch review Bruce Momjian
• 23:10   Re: Patch review Brendan Jurd
• 23:12   Re: Patch review Bruce Momjian
• 23:58   Re: NLS on MSVC strikes back! Hiroshi Saito

13 February 2008

• 00:03   Re: NLS on MSVC strikes back! Hiroshi Saito
• 00:24   Re: Patch review Gregory Stark
• 00:57   Re: Patch review Bruce Momjian
• 01:42   Re: Patch review Gregory Stark
• 02:22   REL8_3_STABLE branch created ... Marc G. Fournier
• 02:39   Branched for 8.4 Bruce Momjian
• 02:42   Locale vs LIKE Stephen Denne
• 02:47   Re: REL8_3_STABLE branch created ... Tom Lane
• 06:53   Re: Locale vs LIKE Gregory Stark
• 07:41   Re: Patch review Greg Smith
• 11:12   Re: Patch review Alvaro Herrera
• 14:27   Re: Patch review Tom Lane
• 14:32   Re: [pgsql-www] Patch review Dave Page
• 16:25   Re: Patch review Greg Smith
• 17:21   Re: Patch review Gregory Stark
• 17:28   Re: Patch review Alvaro Herrera
• 17:33   Stamping of 8.4 Bruce Momjian
• 17:35   Re: Stamping of 8.4 Bruce Momjian
• 19:35   Re: Stamping of 8.4 Alvaro Herrera
• 19:38   Re: Stamping of 8.4 Bruce Momjian
• 19:38   Re: Stamping of 8.4 Tom Lane
• 19:44   Re: Stamping of 8.4 Alvaro Herrera
• 19:50   Re: Stamping of 8.4 Bruce Momjian
• 19:51   Re: Stamping of 8.4 Stephen Frost
• 19:56   Re: Stamping of 8.4 Bruce Momjian
• 19:56   Re: Stamping of 8.4 Tom Lane
• 20:03   Re: Stamping of 8.4 Alvaro Herrera
• 20:27   Re: Stamping of 8.4 Tom Lane
• 20:35   Re: Stamping of 8.4 Bruce Momjian

14 February 2008

• 02:51   Re: Patch review Bruce Momjian
• 03:52   Show INHERIT in \du Brendan Jurd
• 05:21   Re: NLS on MSVC strikes back! Hiroshi Saito
• 05:51   wishlist for 8.4 Raphaël Jacquot
• 05:52   Timezone view Naz Gassiep
• 10:35   Re: Show INHERIT in \du Bernd Helmle
• 12:27   Re: Show INHERIT in \du Alvaro Herrera
• 12:30   Re: wishlist for 8.4 Martijn van Oosterhout
• 12:43   Reworking WAL locking Simon Riggs
• 13:29   Re: Show INHERIT in \du Bernd Helmle
• 15:06   Re: wishlist for 8.4 Tom Lane
• 15:08   Re: Timezone view Tom Lane
• 15:42   Re: Show INHERIT in \du Tom Lane
• 15:49   Re: Reworking WAL locking Tom Lane
• 17:25   Re: Show INHERIT in \du Guillaume Lelarge
• 17:52   Re: Reworking WAL locking Tom Lane
• 18:21   Re: Reworking WAL locking Simon Riggs
• 20:51   Re: Reworking WAL locking Tom Lane
• 21:29   Re: Show INHERIT in \du Alvaro Herrera
• 22:25   Re: Show INHERIT in \du Brendan Jurd
• 22:51   Re: Show INHERIT in \du Tom Lane
• 23:09   Re: Show INHERIT in \du Brendan Jurd

15 February 2008

• 01:58   Re: wishlist for 8.4 Decibel!
• 01:59   Key for grant attributes (was: Re: Show INHERIT in \du) Decibel!
• 02:00   Re: Show INHERIT in \du Decibel!
• 02:13   Re: Key for grant attributes (was: Re: Show INHERIT in \du) Brendan Jurd
• 06:59   ANALYZE to be ignored by VACUUM ITAGAKI Takahiro
• 07:15   Re: Reworking WAL locking Simon Riggs
• 09:07   Re: wishlist for 8.4 Richard Huxton
• 10:43   subquery in limit Grzegorz Jaskiewicz
• 12:05   Re: wishlist for 8.4 Sam Mason
• 12:47   Re: wishlist for 8.4 Heikki Linnakangas
• 12:57   Re: subquery in limit Roberts, Jon
• 14:28   Re: ANALYZE to be ignored by VACUUM Tom Lane
• 14:44   Re: subquery in limit Tom Lane
• 14:46   Re: subquery in limit Roberts, Jon
• 16:37   CVS repository invalid revision Christian Robottom Reis
• 16:38   Last call for objections: SELECT alias without AS for IDENTs only? Tom Lane
• 16:44   Re: wishlist for 8.4 David Fetter
• 18:20   NetBSD/dtime_t Michael Meskes
• 21:07   Re: NetBSD/dtime_t Kris Jurka

16 February 2008

• 01:35   PG-relevant bug fixes just pushed in Fedora 8 Tom Lane
• 08:57   Re: NetBSD/dtime_t Michael Meskes
• 13:15   Re: NetBSD/dtime_t Tom Lane
• 17:02   Replacing time_t fields in pg_control and elsewhere Tom Lane
• 18:28   Re: CVS repository invalid revision Peter Eisentraut

17 February 2008

• 09:56   Re: Show INHERIT in \du Brendan Jurd
• 14:33   Doubt in IndexScanDescData Suresh
• 14:57   Re: Doubt in IndexScanDescData Hans-Juergen Schoenig
• 15:14   Re: Doubt in IndexScanDescData Suresh
• 15:23   Re: Doubt in IndexScanDescData Hans-Juergen Schoenig
• 16:03   Re: Doubt in IndexScanDescData Gregory Stark
• 17:45   Re: NetBSD/dtime_t Michael Meskes
• 18:06   Re: Replacing time_t fields in pg_control and elsewhere Zdenek Kotala
• 21:57   Re: CVS repository invalid revision Christian Robottom Reis

18 February 2008

• 12:18   Error"Failed to run initdb: 128!" Pattu, Susanta Kumar
• 12:30   IDENTITY/GENERATED patch Zoltan Boszormenyi
• 12:36   Error building 32 bit on 64 bit linux system Doug Knight
• 12:44   Error"Failed to run initdb: 128!" Pattu, Susanta Kumar
• 13:18   Re: Error building 32 bit on 64 bit linux system Zdenek Kotala
• 13:48   Re: Error building 32 bit on 64 bit linux system Andrew Dunstan
• 13:53   Re: Error"Failed to run initdb: 128!" Andrew Dunstan
• 13:58   Re: Error building 32 bit on 64 bit linux system Doug Knight
• 17:13   Re: CVS repository invalid revision Alvaro Herrera
• 18:05   Re: Error building 32 bit on 64 bit linux system Tom Lane
• 18:18   Re: Error building 32 bit on 64 bit linux system Zoltan Boszormenyi
• 18:47   Ad Hoc Indexes Justin
• 18:58   Re: [GENERAL] deadlock with truncate and foreing keys Tom Lane
• 19:09   Re: Ad Hoc Indexes Peter Eisentraut
• 19:13   Re: IDENTITY/GENERATED patch Tom Lane
• 19:16   Re: Ad Hoc Indexes Hans-Juergen Schoenig
• 19:18   Re: Ad Hoc Indexes Tom Lane
• 19:59   Re: CVS repository invalid revision Greg Smith
• 20:12   Re: Ad Hoc Indexes Justin
• 20:28   Re: Ad Hoc Indexes Tom Lane
• 20:37   Re: [GENERAL] deadlock with truncate and foreing keys Stephan Szabo
• 20:45   Re: Ad Hoc Indexes Peter Eisentraut
• 20:58   Re: [GENERAL] deadlock with truncate and foreing keys Tom Lane
• 21:12   Re: Ad Hoc Indexes Justin
• 21:17   Re: Ad Hoc Indexes Justin
• 22:31   Severe regression in autoconf 2.61 Tom Lane

19 February 2008

• 00:01   Re: Ad Hoc Indexes Stephen Denne
• 00:17   Re: Severe regression in autoconf 2.61 Bruce Momjian
• 00:34   Re: Ad Hoc Indexes Justin
• 00:36   Re: Severe regression in autoconf 2.61 Tom Lane
• 01:27   Re: Ad Hoc Indexes Stephen Denne
• 01:28   Re: Severe regression in autoconf 2.61 Bruce Momjian
• 01:39   Re: Severe regression in autoconf 2.61 Tom Lane
• 01:55   Re: Ad Hoc Indexes Tom Lane
• 02:59   Re: Ad Hoc Indexes Justin
• 05:07   Re: wishlist for 8.4 James Mansion
• 05:17   Re: Severe regression in autoconf 2.61 Jeremy Drake
• 05:35   Re: IDENTITY/GENERATED patch Zoltan Boszormenyi
• 06:30   Re: ANALYZE to be ignored by VACUUM ITAGAKI Takahiro
• 07:36   RFP: Recursive query in 8.4 Tatsuo Ishii
• 07:56   Re: ANALYZE to be ignored by VACUUM Gregory Stark
• 08:47   Re: Severe regression in autoconf 2.61 Peter Eisentraut
• 12:22   Getting available options Magnus Hagander
• 12:47   Re: Getting available options Dave Page
• 12:56   Re: Getting available options Peter Eisentraut
• 13:00   Re: Getting available options Magnus Hagander
• 13:05   Re: Getting available options Gevik Babakhani
• 13:18   Re: Getting available options Alvaro Herrera
• 13:23   Re: Getting available options Magnus Hagander
• 13:36   Permanent settings Magnus Hagander
• 13:53   Re: Permanent settings Aidan Van Dyk
• 14:11   Re: Permanent settings Roberts, Jon
• 14:12   Re: Common Sub-expression removal Sam Mason
• 14:12   Re: Timezone view Alvaro Herrera
• 14:27   Re: Permanent settings Magnus Hagander
• 14:34   Re: Permanent settings Aidan Van Dyk
• 14:36   Re: Severe regression in autoconf 2.61 Tom Lane
• 14:38   Re: Permanent settings Csaba Nagy
• 14:39   Re: Permanent settings Magnus Hagander
• 14:41   Re: Permanent settings Magnus Hagander
• 14:53   Re: Permanent settings Richard Huxton
• 14:55   Re: Permanent settings Csaba Nagy
• 14:56   Re: Permanent settings Magnus Hagander
• 15:01   Re: Permanent settings Richard Huxton
• 15:09   Re: Permanent settings Aidan Van Dyk
• 15:11   Re: Permanent settings Aidan Van Dyk
• 15:12   Re: Permanent settings Andrew Dunstan
• 15:25   Re: Permanent settings Magnus Hagander
• 15:30   Re: Permanent settings Andrew Dunstan
• 15:31   Re: Permanent settings Magnus Hagander
• 15:33   Re: Permanent settings Magnus Hagander
• 15:37   Re: Permanent settings Greg Sabino Mullane
• 15:47   Including PL/PgSQL by default David Fetter
• 16:00   Re: Permanent settings Gregory Stark
• 16:12   Re: Including PL/PgSQL by default Tom Lane
• 16:20   Re: Permanent settings Alvaro Herrera
• 16:35   Re: Severe regression in autoconf 2.61 Tom Lane
• 16:38   Re: Including PL/PgSQL by default David Fetter
• 16:43   Re: Permanent settings Roberts, Jon
• 16:52   Re: Including PL/PgSQL by default Tom Lane
• 16:56   Re: CVS repository invalid revision Joshua D. Drake
• 17:09   Re: Permanent settings Joshua D. Drake
• 17:24   Re: Permanent settings Alvaro Herrera
• 17:27   Re: Permanent settings Tom Lane
• 17:29   Re: Permanent settings Joshua D. Drake
• 17:39   Re: Permanent settings Andrew Dunstan
• 18:23   Re: Permanent settings Magnus Hagander
• 18:28   Re: Permanent settings Magnus Hagander
• 18:41   Re: Permanent settings Andrew Dunstan
• 18:43   Re: Permanent settings Gregory Stark
• 19:48   Re: Permanent settings Magnus Hagander
• 20:19   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 20:34   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 20:48   Question regarding TODO item:Allow to_date() and to_timestamp() accept localized month names Gevik Babakhani
• 20:49   Re: Permanent settings Josh Berkus
• 21:03   Re: Permanent settings Magnus Hagander
• 21:18   Re: pg_dump additional options for performance Jeff Davis
• 21:56   Re: Permanent settings Josh Berkus
• 22:05   Re: Permanent settings Bruce Momjian
• 22:14   Re: Including PL/PgSQL by default Andrew Dunstan
• 22:24   Re: Including PL/PgSQL by default Neil Conway
• 22:28   Re: Including PL/PgSQL by default Joshua D. Drake
• 22:30   Re: Permanent settings Josh Berkus
• 22:31   Re: Including PL/PgSQL by default Joshua D. Drake
• 22:49   Re: Including PL/PgSQL by default Andrew Dunstan
• 23:52   Re: Including PL/PgSQL by default Tom Lane

20 February 2008

• 00:08   Re: Permanent settings Tom Lane
• 00:33   gateway test ... Marc G. Fournier
• 00:34   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 00:38   Re: Including PL/PgSQL by default Andrew Dunstan
• 00:40   testing a post directly on server Marc G. Fournier
• 00:56   gateway test II Marc G. Fournier
• 01:32   minimal update trigger Andrew Dunstan
• 03:12   Re: 8.3 / 8.2.6 restore comparison Luke Lonergan
• 03:17   Re: ANALYZE to be ignored by VACUUM ITAGAKI Takahiro
• 03:20   Re: Permanent settings Robert Treat
• 03:36   Re: Permanent settings Robert Treat
• 05:19   distibuted transactions, SQL+XPath+XTree Тюрин Дмитрий
• 07:04   Re: Permanent settings tomas@tuxteam.de
• 07:52   Re: Permanent settings Magnus Hagander
• 07:55   longest prefix match Dragan Zubac
• 08:04   Re: Permanent settings Magnus Hagander
• 08:05   Re: distibuted transactions, SQL+XPath+XTree Richard Huxton
• 08:08   Re: Permanent settings Dawid Kuroczko
• 08:37   Re: longest prefix match Dimitri Fontaine
• 09:20   Re: Permanent settings Dimitri Fontaine
• 09:39   failed assertion in toasting code Sergey E. Koposov
• 10:05   Re: failed assertion in toasting code Gregory Stark
• 10:06   Re: failed assertion in toasting code Teodor Sigaev
• 10:30   Re: failed assertion in toasting code Gregory Stark
• 10:46   Re: Permanent settings Magnus Hagander
• 10:55   Re: failed assertion in toasting code Gregory Stark
• 11:17   Re: failed assertion in toasting code Sergey E. Koposov
• 11:19   Re: failed assertion in toasting code Sergey E. Koposov
• 11:24   generating non-unicode 8-bit text data in SQL_ASCII encoding Gregory Stark
• 11:26   More char()/ascii() Gregory Stark
• 11:28   Re: distibuted transactions, SQL+XPath+XTree Dmitry Turin
• 11:37   Re: Permanent settings Alvaro Herrera
• 11:47   Re: failed assertion in toasting code Gregory Stark
• 11:56   Re: More char()/ascii() Andrew Dunstan
• 12:00   Re: Permanent settings Magnus Hagander
• 12:06   Re: failed assertion in toasting code Sergey E. Koposov
• 12:23   Re: Permanent settings Alvaro Herrera
• 12:26   Re: More char()/ascii() Gregory Stark
• 12:32   Re: Including PL/PgSQL by default Andrew Sullivan
• 12:33   Re: Permanent settings Magnus Hagander
• 13:01   Re: Permanent settings Dimitri Fontaine
• 13:42   Re: Permanent settings Andrew Dunstan
• 14:02   Re: minimal update trigger David Fetter
• 14:07   Re: Permanent settings Dimitri Fontaine
• 14:17   Re: minimal update trigger Andrew Dunstan
• 15:44   Re: Timezone view Naz Gassiep
• 15:44   Re: Timezone view Naz Gassiep
• 15:46   Re: ANALYZE to be ignored by VACUUM Dawid Kuroczko
• 15:50   Re: Permanent settings Tom Lane
• 16:51   Re: More char()/ascii() Tom Lane
• 16:57   Re: Permanent settings Josh Berkus
• 17:08   Re: Permanent settings Josh Berkus
• 17:29   Re: Permanent settings Tom Lane
• 17:34   Re: Permanent settings Tom Lane
• 17:38   Re: Permanent settings Magnus Hagander
• 17:43   Re: Permanent settings Joshua D. Drake
• 17:44   Re: Permanent settings Tom Lane
• 17:55   Re: Permanent settings Aidan Van Dyk
• 17:56   Re: Permanent settings Magnus Hagander
• 18:00   Re: Permanent settings Joshua D. Drake
• 18:03   Re: Permanent settings Magnus Hagander
• 18:31   Re: Permanent settings Aidan Van Dyk
• 18:45   Re: CVS repository invalid revision Christian Robottom Reis
• 19:16   Which MemoryContext? Gevik Babakhani
• 19:23   Re: CVS repository invalid revision Tom Lane
• 19:40   Re: Permanent settings Tom Lane
• 19:41   Re: Permanent settings Magnus Hagander
• 19:47   Re: Permanent settings Tom Lane
• 19:49   Re: Permanent settings Magnus Hagander
• 19:57   Why does pg_ctl.c have its own copy of PM_VERSIONSTR? Tom Lane
• 19:58   Re: Which MemoryContext? Heikki Linnakangas
• 20:20   Re: Why does pg_ctl.c have its own copy of PM_VERSIONSTR? Andrew Dunstan
• 20:27   Re: Permanent settings Dawid Kuroczko
• 20:35   Re: Why does pg_ctl.c have its own copy of PM_VERSIONSTR? Tom Lane
• 21:00   Re: CVS repository invalid revision Aidan Van Dyk
• 21:08   Re: Getting available options Simon Riggs
• 21:11   Re: CVS repository invalid revision Andrew Dunstan
• 21:16   Re: CVS repository invalid revision Christian Robottom Reis
• 21:31   Re: CVS repository invalid revision Aidan Van Dyk
• 21:32   Re: CVS repository invalid revision Andrew Dunstan
• 21:32   Re: CVS repository invalid revision Heikki Linnakangas
• 21:33   Re: CVS repository invalid revision Aidan Van Dyk
• 21:53   Re: CVS repository invalid revision Aidan Van Dyk
• 21:58   Re: Permanent settings Josh Berkus
• 21:59   Re: Getting available options Tom Lane
• 22:12   Re: Which MemoryContext? Gevik Babakhani
• 22:17   Re: Permanent settings Aidan Van Dyk
• 22:38   Re: Permanent settings Tom Lane
• 22:39   Re: Permanent settings Bruce Momjian
• 22:48   Re: Which MemoryContext? Heikki Linnakangas
• 22:49   Re: Permanent settings Joshua D. Drake
• 22:50   Re: Permanent settings Joshua D. Drake
• 22:52   Re: Which MemoryContext? Gevik Babakhani
• 22:53   Re: Permanent settings Gregory Stark
• 22:56   Re: Permanent settings paul rivers
• 23:12   Re: Permanent settings Dawid Kuroczko

21 February 2008

• 00:20   Re: Including PL/PgSQL by default Greg Sabino Mullane
• 01:12   Re: Permanent settings Joshua D. Drake
• 02:52   Re: Permanent settings Andrew Dunstan
• 03:02   Re: Permanent settings Aidan Van Dyk
• 03:05   Re: Which MemoryContext? Alvaro Herrera
• 03:06   Re: Permanent settings Joshua D. Drake
• 03:25   Batch update of indexes on data loading ITAGAKI Takahiro
• 03:35   Re: ANALYZE to be ignored by VACUUM ITAGAKI Takahiro
• 04:40   Re: Including PL/PgSQL by default Tom Lane
• 05:08   VARATT_EXTERNAL_GET_POINTER is not quite there yet Tom Lane
• 06:38   Re: Permanent settings Peter Childs
• 07:05   Re: Which MemoryContext? Gevik Babakhani
• 08:12   Re: VARATT_EXTERNAL_GET_POINTER is not quite there yet Gregory Stark
• 08:18   Re: Permanent settings Magnus Hagander
• 08:20   Re: Permanent settings Magnus Hagander
• 08:23   Re: Permanent settings Magnus Hagander
• 08:25   Re: Permanent settings Magnus Hagander
• 08:28   Re: Permanent settings Magnus Hagander
• 08:30   Re: Permanent settings Magnus Hagander
• 08:34   Re: Permanent settings Magnus Hagander
• 09:17   TO_DATE behavior! Gevik Babakhani
• 09:35   Re: TO_DATE behavior! Peter Eisentraut
• 09:38   Re: TO_DATE behavior! Gevik Babakhani
• 10:09   about date/time parser Gevik Babakhani
• 10:37   Re: Getting available options Magnus Hagander
• 11:15   Re: Getting available options Alvaro Herrera
• 11:23   Re: Getting available options Magnus Hagander
• 13:28   Re: Batch update of indexes on data loading Alvaro Herrera
• 13:30   insufficient data left in message Dave Cramer
• 13:35   Re: Permanent settings Alexey Klyukin
• 13:54   Re: Timezone view Martijn van Oosterhout
• 14:03   Re: Permanent settings Joshua D. Drake
• 14:05   Re: Permanent settings Aidan Van Dyk
• 14:19   Re: Permanent settings D'Arcy J.M. Cain
• 14:40   Re: insufficient data left in message Tom Lane
• 14:42   Re: Permanent settings Greg Sabino Mullane
• 14:43   Re: Permanent settings Kevin Grittner
• 14:58   Re: Permanent settings Zdenek Kotala
• 14:59   Re: Permanent settings Joshua D. Drake
• 15:08   OSSP can be used in the windows environment now! Hiroshi Saito
• 15:51   Re: Permanent settings Zdenek Kotala
• 15:53   Re: Permanent settings Ron Mayer
• 16:13   Re: VARATT_EXTERNAL_GET_POINTER is not quite there yet Tom Lane
• 16:23   Re: TO_DATE behavior! Tom Lane
• 16:28   Re: about date/time parser Tom Lane
• 16:29   Re: Permanent settings Mark Woodward
• 16:33   Re: insufficient data left in message Dave Cramer
• 16:34   Re: Including PL/PgSQL by default Greg Sabino Mullane
• 16:37   Re: Permanent settings Andrew Dunstan
• 16:49   Re: Permanent settings Mark Woodward
• 16:53   Re: Including PL/PgSQL by default Joshua D. Drake
• 16:54   Re: Including PL/PgSQL by default Josh Berkus
• 16:56   Re: Permanent settings Andrew Dunstan
• 17:01   Re: about date/time parser Gevik Babakhani
• 17:02   Re: Including PL/PgSQL by default Joshua D. Drake
• 17:24   Re: insufficient data left in message Tom Lane
• 17:35   Re: Including PL/PgSQL by default Andrew Dunstan
• 17:39   Re: Including PL/PgSQL by default Tom Lane
• 17:41   Re: Including PL/PgSQL by default Joshua D. Drake
• 17:44   Re: Including PL/PgSQL by default Joshua D. Drake
• 17:52   Re: VARATT_EXTERNAL_GET_POINTER is not quite there yet Gregory Stark
• 17:56   Re: Including PL/PgSQL by default Roberts, Jon
• 18:15   Re: Including PL/PgSQL by default Andrew Sullivan
• 18:15   Re: Including PL/PgSQL by default Tom Lane
• 18:16   Re: Including PL/PgSQL by default Andrew Dunstan
• 18:29   Re: Including PL/PgSQL by default Alvaro Herrera
• 18:41   Re: Including PL/PgSQL by default D'Arcy J.M. Cain
• 18:42   Re: Including PL/PgSQL by default Tom Lane
• 18:51   Re: Including PL/PgSQL by default Joshua D. Drake
• 18:59   Re: VARATT_EXTERNAL_GET_POINTER is not quite there yet Tom Lane
• 19:16   Re: Including PL/PgSQL by default Andrew Dunstan
• 23:57   Re: Batch update of indexes on data loading ITAGAKI Takahiro

22 February 2008

• 01:16   Memory leaks on SRF rescan Neil Conway
• 01:24   Re: Including PL/PgSQL by default Josh Berkus
• 01:26   Re: Batch update of indexes on data loading Josh Berkus
• 01:33   Re: Including PL/PgSQL by default Tom Lane
• 01:42   Re: Memory leaks on SRF rescan Tom Lane
• 01:53   Re: Memory leaks on SRF rescan Neil Conway
• 02:03   Re: Including PL/PgSQL by default Marc G. Fournier
• 02:07   Re: Memory leaks on SRF rescan Tom Lane
• 03:30   Re: [PATCHES] 2WRS [WIP] Jaime Casanova
• 04:42   Re: RFP: Recursive query in 8.4 ITAGAKI Takahiro
• 06:38   Re: Including PL/PgSQL by default Dave Page
• 06:48   Linking backend in one piece Peter Eisentraut
• 06:53   Re: Linking backend in one piece Dave Page
• 08:53   Re: Including PL/PgSQL by default Peter Eisentraut
• 09:00   Re: Including PL/PgSQL by default Joshua D. Drake
• 09:36   Full-text search default vs specified configuration Richard Huxton
• 10:18   Re: Permanent settings Tino Wildenhain
• 11:07   Re: OSSP can be used in the windows environment now! Magnus Hagander
• 13:15   Re: Including PL/PgSQL by default Alvaro Herrera
• 14:15   Re: Linking backend in one piece Alvaro Herrera
• 14:16   Re: Linking backend in one piece Tom Lane
• 14:23   Re: RFP: Recursive query in 8.4 Tatsuo Ishii
• 14:28   Re: Including PL/PgSQL by default Andrew Dunstan
• 14:47   Re: Including PL/PgSQL by default Roberts, Jon
• 14:56   Re: Linking backend in one piece Peter Eisentraut
• 15:03   Re: Including PL/PgSQL by default D'Arcy J.M. Cain
• 15:04   Re: Linking backend in one piece Peter Eisentraut
• 15:09   Re: Including PL/PgSQL by default Andrew Dunstan
• 15:26   Re: Linking backend in one piece Alvaro Herrera
• 15:46   Re: Including PL/PgSQL by default Tom Lane
• 15:53   Re: Linking backend in one piece Tom Lane
• 15:58   Re: Including PL/PgSQL by default Jeremy Drake
• 16:07   Re: Linking backend in one piece Peter Eisentraut
• 16:12   Re: Including PL/PgSQL by default Andrew Satori
• 16:19   Re: Including PL/PgSQL by default Greg Sabino Mullane
• 16:23   Proposed changes to DTrace probe implementation Robert Lor
• 16:23   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 16:24   Re: Full-text search default vs specified configuration Tom Lane
• 16:28   Re: Linking backend in one piece Tom Lane
• 16:28   Re: Including PL/PgSQL by default Andrew Dunstan
• 16:31   Re: Including PL/PgSQL by default Tom Lane
• 16:37   Re: Including PL/PgSQL by default Joshua D. Drake
• 16:40   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 16:44   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 16:50   Re: Including PL/PgSQL by default Tom Lane
• 16:54   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 16:54   Re: Including PL/PgSQL by default Martijn van Oosterhout
• 17:02   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 17:09   Re: Proposed changes to DTrace probe implementation Peter Eisentraut
• 17:42   Re: Including PL/PgSQL by default Kevin Grittner
• 17:44   Re: Full-text search default vs specified configuration Richard Huxton
• 17:56   Re: Proposed changes to DTrace probe implementation Robert Lor
• 18:02   Re: OSSP can be used in the windows environment now! Hiroshi Saito
• 18:10   Re: Proposed changes to DTrace probe implementation Robert Lor
• 18:15   Re: Including PL/PgSQL by default Josh Berkus
• 18:53   Re: RFP: Recursive query in 8.4 Merlin Moncure
• 20:28   Re: Full-text search default vs specified configuration Oleg Bartunov
• 20:37   Improved (De)Serialization Support Andy Pavlo

23 February 2008

• 04:17   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 04:40   Re: Improved (De)Serialization Support Tom Lane
• 05:31   Re: 8.3 / 8.2.6 restore comparison Greg Smith
• 05:53   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 11:34   Re: [PATCHES] Avahi support for Postgresql Mathias Hasselmann
• 16:52   Re: 8.3 / 8.2.6 restore comparison Stefan Kaltenbrunner
• 17:06   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 17:31   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 17:47   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 17:54   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 17:59   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 18:24   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 18:36   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 18:39   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 18:41   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 19:15   Re: [PATCHES] Avahi support for Postgresql Peter Eisentraut
• 20:19   Re: [PATCHES] Avahi support for Postgresql Mathias Hasselmann
• 23:44   Re: 8.3 / 8.2.6 restore comparison Heikki Linnakangas

24 February 2008

• 00:46   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 08:39   Re: 8.3 / 8.2.6 restore comparison Heikki Linnakangas
• 08:44   Re: 8.3 / 8.2.6 restore comparison Heikki Linnakangas
• 09:53   Re: RFP: Recursive query in 8.4 Tatsuo Ishii
• 10:52   Re: RFP: Recursive query in 8.4 Gregory Stark
• 12:22   Re: pg_dump additional options for performance Jochem van Dieten
• 13:29   Re: 8.3 / 8.2.6 restore comparison andy
• 15:54   idea: simple variadic functions in SQL and PL/pgSQL Pavel Stehule
• 15:55   Behaviour of rows containg not-null domains in plpgsql Florian G. Pflug
• 16:28   Re: Behaviour of rows containg not-null domains in plpgsql Andrew Dunstan
• 16:32   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 16:38   Re: Behaviour of rows containg not-null domains in plpgsql Florian G. Pflug
• 16:40   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 16:41   Re: 8.3 / 8.2.6 restore comparison Hannes Dorbath
• 16:47   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 16:57   Re: Behaviour of rows containg not-null domains in plpgsql Tom Lane
• 17:04   Re: Improved (De)Serialization Support Andy Pavlo
• 17:06   Re: 8.3 / 8.2.6 restore comparison Andrew Dunstan
• 17:10   Re: Behaviour of rows containg not-null domains in plpgsql Tom Lane
• 17:12   Re: 8.3 / 8.2.6 restore comparison Tom Lane
• 17:23   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 17:25   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 18:07   Re: Behaviour of rows containg not-null domains in plpgsql Florian G. Pflug
• 18:18   Re: Behaviour of rows containg not-null domains in plpgsql Tom Lane
• 18:27   Re: Behaviour of rows containg not-null domains in plpgsql Florian G. Pflug
• 18:28   Re: Batch update of indexes on data loading Simon Riggs
• 20:31   insert ... delete ... returning ... ? Mark Mielke
• 20:39   Re: insert ... delete ... returning ... ? Guillaume Smet
• 20:43   Re: insert ... delete ... returning ... ? Guillaume Smet
• 20:43   Re: insert ... delete ... returning ... ? Jonah H. Harris
• 21:44   Re: insert ... delete ... returning ... ? Tom Lane
• 22:14   Re: insert ... delete ... returning ... ? Jonah H. Harris
• 22:52   Re: insert ... delete ... returning ... ? Mark Mielke

25 February 2008

• 02:45   dblink doesn't honor interrupts while waiting a result Florian G. Pflug
• 04:39   Re: pg_dump additional options for performance Pavan Deolasee
• 05:22   Re: insert ... delete ... returning ... ? Tom Lane
• 08:06   Re: pg_dump additional options for performance Tom Dunstan
• 08:44   Re: OSSP can be used in the windows environment now! Hiroshi Saito
• 09:35   Re: dblink doesn't honor interrupts while waiting a result Marko Kreen
• 09:52   Re: dblink doesn't honor interrupts while waiting a result Florian G. Pflug
• 12:15   Questions about indexes with text_pattern_ops Kaare Rasmussen
• 12:50   Smaller db in 8.3 (was: Re: insert ... delete ... returning ... ?) Mark Mielke
• 13:05   Re: [PATCHES] Avahi support for Postgresql Peter Eisentraut
• 13:10   One more option for pg_dump... David BOURIAUD
• 13:23   Re: [PATCHES] Avahi support for Postgresql Peter Eisentraut
• 13:33   Re: [PATCHES] Avahi support for Postgresql Alvaro Herrera
• 13:38   Re: One more option for pg_dump... Leonardo Cezar
• 14:00   Re: Questions about indexes with text_pattern_ops Gregory Stark
• 14:14   Strange behavior with leap dates and centuries BC Bernd Helmle
• 14:33   Re: One more option for pg_dump... David BOURIAUD
• 14:51   Re: Questions about indexes with text_pattern_ops Tom Lane
• 15:00   Tuning 8.3 Roberts, Jon
• 15:04   Re: [PATCHES] Avahi support for Postgresql Peter Eisentraut
• 15:11   Re: Tuning 8.3 Andrew Dunstan
• 15:14   Re: Questions about indexes with text_pattern_ops Gregory Stark
• 15:24   Re: Tuning 8.3 Gregory Stark
• 15:30   Re: Questions about indexes with text_pattern_ops Tom Lane
• 15:48   Re: Tuning 8.3 Roberts, Jon
• 16:00   Re: Strange behavior with leap dates and centuries BC Tom Lane
• 16:10   Re: Questions about indexes with text_pattern_ops Gregory Stark
• 16:33   Re: [PATCHES] Avahi support for Postgresql Alvaro Herrera
• 16:37   pgAgent job throttling Roberts, Jon
• 16:40   Re: Questions about indexes with text_pattern_ops Tom Lane
• 17:06   Re: Questions about indexes with text_pattern_ops Gregory Stark
• 17:08   Re: Strange behavior with leap dates and centuries BC Bernd Helmle
• 17:10   Re: build environment: a different makefile Peter Eisentraut
• 17:20   Re: One more option for pg_dump... Leonardo Cezar
• 17:54   Re: Questions about indexes with text_pattern_ops Tom Lane
• 18:04   Re: Strange behavior with leap dates and centuries BC Tom Lane
• 18:27   Re: [PATCHES] Avahi support for Postgresql Mathias Hasselmann
• 18:29   libpq.rc make rule Peter Eisentraut
• 18:44   Re: [PATCHES] Avahi support for Postgresql Tom Lane
• 18:47   Re: 8.3 / 8.2.6 restore comparison Jeff Davis
• 18:50   Re: [PATCHES] Avahi support for Postgresql Mathias Hasselmann
• 19:07   Re: Tuning 8.3 Christopher Browne
• 19:10   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 19:11   Re: [PATCHES] Avahi support for Postgresql Tom Lane
• 19:17   Re: 8.3 / 8.2.6 restore comparison Jeff Davis
• 19:22   Re: Strange behavior with leap dates and centuries BC Bernd Helmle
• 19:28   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 20:36   Re: libpq.rc make rule Dave Page
• 21:03   Re: libpq.rc make rule Peter Eisentraut
• 21:06   Re: 8.3 / 8.2.6 restore comparison Jeff Davis
• 21:11   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 21:33   Re: libpq.rc make rule Dave Page
• 22:11   Re: idea: simple variadic functions in SQL and PL/pgSQL Andrew Dunstan
• 22:48   Re: libpq.rc make rule Peter Eisentraut
• 23:15   Re: libpq.rc make rule Dave Page

26 February 2008

• 01:42   Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the D'Arcy J.M. Cain
• 01:53   Reference by in \d out kenneth d'souza
• 02:00   Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the Tom Lane
• 04:19   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 04:39   Re: pg_dump additional options for performance Tom Lane
• 05:19   Re: 8.3 / 8.2.6 restore comparison Jeff Davis
• 05:19   Re: Batch update of indexes on data loading ITAGAKI Takahiro
• 05:25   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 05:36   Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the Peter Eisentraut
• 05:38   Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the Tom Lane
• 07:32   code cleanup of timestamp code Warren Turkal
• 08:08   Re: Batch update of indexes on data loading Simon Riggs
• 08:26   Re: libpq.rc make rule Magnus Hagander
• 08:37   Re: code cleanup of timestamp code Martijn van Oosterhout
• 09:23   Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the Peter Eisentraut
• 09:59   Producer/Consumer Issues in the COPY across network Simon Riggs
• 10:05   Re: pg_dump additional options for performance Simon Riggs
• 10:22   Re: pg_dump additional options for performance Simon Riggs
• 10:30   Re: Producer/Consumer Issues in the COPY across network Martijn van Oosterhout
• 10:31   Re: pg_dump additional options for performance Magnus Hagander
• 11:14   Re: pg_dump additional options for performance Dimitri Fontaine
• 11:22   Re: pg_dump additional options for performance Simon Riggs
• 11:49   Re: pg_dump additional options for performance Tom Dunstan
• 12:05   Re: pg_dump additional options for performance Simon Riggs
• 12:29   Re: pg_dump additional options for performance Zeugswetter Andreas ADI SD
• 12:33   Re: [PATCHES] 2WRS [WIP] 
• 12:35   Re: pg_dump additional options for performance Andrew Dunstan
• 12:36   Re: Reference by in \d out Alvaro Herrera
• 12:38   Re: pg_dump additional options for performance Dimitri Fontaine
• 12:43   pgAgent job limit Roberts, Jon
• 13:03   Re: pgAgent job limit Andrew Dunstan
• 13:12   Re: pg_dump additional options for performance Magnus Hagander
• 13:14   Re: pgAgent job limit Roberts, Jon
• 13:15   Re: pg_dump additional options for performance Simon Riggs
• 13:16   Re: pgAgent job limit Alvaro Herrera
• 13:16   Re: pgAgent job limit Magnus Hagander
• 13:26   Re: pg_dump additional options for performance Simon Riggs
• 13:28   Re: pg_dump additional options for performance Ron Mayer
• 13:36   Re: pgAgent job limit Roberts, Jon
• 13:45   Bulk loading performance improvements Simon Riggs
• 14:04   Re: pg_dump additional options for performance Tom Lane
• 14:11   Re: [PATCHES] 2WRS [WIP] 
• 14:12   Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the Tom Lane
• 14:15   Re: pg_dump additional options for performance Simon Riggs
• 14:16   Re: pg_dump additional options for performance Andrew Dunstan
• 14:23   Re: pg_dump additional options for performance David BOURIAUD
• 14:25   Re: Bulk loading performance improvements Gregory Stark
• 14:28   Re: pg_dump additional options for performance Magnus Hagander
• 14:31   Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the Andrew Dunstan
• 14:35   Re: Bulk loading performance improvements Simon Riggs
• 14:42   Re: Proposed changes to DTrace probe implementation Robert Lor
• 14:43   Re: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 14:46   Re: pg_dump additional options for performance Simon Riggs
• 14:49   Re: pg_dump additional options for performance Tom Lane
• 15:42   Re: Proposed changes to DTrace probe implementation Tom Lane
• 15:59   Re: pg_dump additional options for performance Tom Lane
• 16:00   Re: Including PL/PgSQL by default Robert Treat
• 16:06   Re: Including PL/PgSQL by default Alvaro Herrera
• 16:16   Re: pg_dump additional options for performance Simon Riggs
• 16:20   Varlena Type Creation Dimitri Fontaine
• 16:21   Re: Including PL/PgSQL by default Andrew Dunstan
• 16:24   Re: pg_dump additional options for performance Simon Riggs
• 16:29   Re: pg_dump additional options for performance Greg Smith
• 16:36   Re: Including PL/PgSQL by default Tom Lane
• 16:44   Re: [COMMITTERS] pgsql: Don't build the win32 support files in the all target, only in Peter Eisentraut
• 16:54   Idle idea for improving concurrency of LISTEN/NOTIFY Tom Lane
• 17:05   Re: pg_dump additional options for performance Tom Lane
• 17:14   Re: pg_dump additional options for performance Simon Riggs
• 17:20   Re: pg_dump additional options for performance Tom Lane
• 17:33   Re: pg_dump additional options for performance Andrew Dunstan
• 17:39   Re: pg_dump additional options for performance Jeff Davis
• 17:53   Re: Proposed changes to DTrace probe implementation Robert Lor
• 17:54   Re: pg_dump additional options for performance Joshua D. Drake
• 18:01   Re: code cleanup of timestamp code Neil Conway
• 18:02   Re: Proposed changes to DTrace probe implementation Tom Lane
• 18:07   Re: pg_dump additional options for performance Tom Lane
• 18:19   Re: pg_dump additional options for performance Joshua D. Drake
• 18:41   Re: pg_dump additional options for performance Greg Smith
• 18:43   Re: pg_dump additional options for performance Alvaro Herrera
• 19:00   Re: pg_dump additional options for performance Simon Riggs
• 19:03   Re: Proposed changes to DTrace probe implementation Robert Lor
• 19:04   Re: pg_dump additional options for performance Joshua D. Drake
• 19:05   Re: pg_dump additional options for performance Simon Riggs
• 19:06   Re: pg_dump additional options for performance Simon Riggs
• 19:06   Re: code cleanup of timestamp code Tom Lane
• 19:07   Re: Including PL/PgSQL by default Josh Berkus
• 19:07   Re: pg_dump additional options for performance Tom Lane
• 19:08   Re: code cleanup of timestamp code Neil Conway
• 19:09   Two Coverity Scan volunteers needed Josh Berkus
• 19:22   Re: Proposed changes to DTrace probe implementation Gregory Stark
• 19:26   Re: Two Coverity Scan volunteers needed Neil Conway
• 19:44   Re: Including PL/PgSQL by default Robert Treat
• 19:49   Re: pg_dump additional options for performance Gregory Stark
• 20:14   Required make version Peter Eisentraut
• 20:48   Re: Proposed changes to DTrace probe implementation Robert Lor
• 21:04   Re: Required make version Tom Lane
• 21:14   Re: Proposed changes to DTrace probe implementation Tom Lane
• 21:37   Re: pg_dump additional options for performance Tom Lane
• 21:49   Re: Two Coverity Scan volunteers needed Josh Berkus
• 21:51   Re: Mailing list failure WAS: Including PL/PgSQL by default Josh Berkus
• 21:57   Re: Two Coverity Scan volunteers needed Joshua D. Drake
• 21:57   Re: Mailing list failure WAS: Including PL/PgSQL by default Joshua D. Drake
• 22:17   multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 22:42   Re: multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison Tom Lane
• 22:53   Re: Two Coverity Scan volunteers needed Neil Conway
• 22:53   Re: Required make version Andrew Dunstan
• 22:53   Re: multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 22:59   Re: Required make version Tom Lane
• 23:04   Re: multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison Tom Lane
• 23:24   Re: multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison Joshua D. Drake
• 23:50   Re: Required make version Peter Eisentraut
• 23:56   Re: Two Coverity Scan volunteers needed Andrej Ricnik-Bay

27 February 2008

• 01:03   Re: pg_dump additional options for performance Gregory Stark
• 01:05   Re: One more option for pg_dump... Brendan Jurd
• 01:09   Re: Mailing list failure WAS: Including PL/PgSQL by default Marc G. Fournier
• 01:36   Re: Proposed changes to DTrace probe implementation Robert Lor
• 01:43   An idea for parallelizing COPY within one backend Florian G. Pflug
• 02:29   Re: One more option for pg_dump... Joshua D. Drake
• 02:41   Re: One more option for pg_dump... Brendan Jurd
• 03:47   Re: An idea for parallelizing COPY within one backend Tom Lane
• 05:28   Re: Required make version Tom Lane
• 07:08   Re: pg_dump additional options for performance Simon Riggs
• 07:09   Re: An idea for parallelizing COPY within one backend Dimitri Fontaine
• 07:19   Re: Two Coverity Scan volunteers needed Martijn van Oosterhout
• 08:28   Re: Proposed changes to DTrace probe implementation Magnus Hagander
• 08:53   Re: pg_dump additional options for performance Dimitri Fontaine
• 09:02   win32 build problem (cvs, msvc 2005 express) craigp
• 09:06   Re: win32 build problem (cvs, msvc 2005 express) Magnus Hagander
• 09:19   Re: pg_dump additional options for performance Dimitri Fontaine
• 09:47   Re: An idea for parallelizing COPY within one backend Simon Riggs
• 10:31   Full text search - altering the default parser Richard Huxton
• 10:47   Re: OSSP can be used in the windows environment now! Magnus Hagander
• 11:42   Proposal: wildcards in pg_service.conf Albe Laurenz
• 11:46   Re: OSSP can be used in the windows environment now! Hiroshi Saito
• 11:48   Re: An idea for parallelizing COPY within one backend Florian G. Pflug
• 12:00   Re: Required make version Alvaro Herrera
• 12:55   Re: Required make version Alvaro Herrera
• 13:11   Re: An idea for parallelizing COPY within one backend Florian G. Pflug
• 13:13   select avanced cristianopintado@gmail.com
• 13:25   proposal: plpgsql return execute ... Pavel Stehule
• 13:26   Re: idea: simple variadic functions in SQL and PL/pgSQL Pavel Stehule
• 13:29   Re: OSSP can be used in the windows environment now! Magnus Hagander
• 13:35   Re: select avanced Richard Huxton
• 14:00   Re: An idea for parallelizing COPY within one backend A.M.
• 14:05   Re: An idea for parallelizing COPY within one backend Brian Hurt
• 14:10   Re: An idea for parallelizing COPY within one backend Alvaro Herrera
• 14:37   Re: Proposal: wildcards in pg_service.conf Tom Lane
• 14:53   Re: An idea for parallelizing COPY within one backend Heikki Linnakangas
• 14:56   Re: An idea for parallelizing COPY within one backend Florian G. Pflug
• 15:15   Re: Proposed changes to DTrace probe implementation Paul van den Bogaard
• 15:33   Re: An idea for parallelizing COPY within one backend Tom Dunstan
• 15:34   Re: OSSP can be used in the windows environment now! Hiroshi Saito
• 15:41   Re: An idea for parallelizing COPY within one backend Tom Lane
• 15:46   Re: An idea for parallelizing COPY within one backend Andrew Dunstan
• 15:53   Re: An idea for parallelizing COPY within one backend Brian Hurt
• 15:56   ResourceOwners for Snapshots? holdable portals Alvaro Herrera
• 16:03   Re: An idea for parallelizing COPY within one backend Florian G. Pflug
• 16:16   Re: An idea for parallelizing COPY within one backend Tom Lane
• 16:47   Re: An idea for parallelizing COPY within one backend Florian G. Pflug
• 16:53   Re: ResourceOwners for Snapshots? holdable portals Tom Lane
• 17:58   Re: proposal: plpgsql return execute ... Neil Conway
• 18:08   Re: ResourceOwners for Snapshots? holdable portals Alvaro Herrera
• 18:21   Re: Required make version Peter Eisentraut
• 19:08   Re: proposal: plpgsql return execute ... Merlin Moncure
• 19:13   Re: OSSP can be used in the windows environment now! Magnus Hagander
• 19:33   Idea for minor tstore optimization Neil Conway
• 19:34   Re: [PATCHES] 2WRS [WIP] 
• 20:35   Re: proposal: plpgsql return execute ... Pavel Stehule
• 21:03   new warning message Jeff Davis
• 21:10   Re: Varlena Type Creation Martijn van Oosterhout
• 21:43   Re: new warning message Tom Lane
• 21:44   Snapshot Reuse Simon Riggs
• 21:48   Re: Idea for minor tstore optimization Tom Lane
• 22:15   UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Dawid Kuroczko
• 22:53   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Josh Berkus
• 23:13   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Gevik Babakhani
• 23:19   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Tom Lane
• 23:38   Re: OSSP can be used in the windows environment now! Hiroshi Saito
• 23:53   Buildfarm member gypsy_moth seems not to like alignment patch Tom Lane

28 February 2008

• 00:56   Re: Producer/Consumer Issues in the COPY across network Simon Riggs
• 06:14   Re: Batch update of indexes on data loading ITAGAKI Takahiro
• 06:51   ES7000 Windows 2003 server 64bit processor Babu, Gabriel Suresh
• 07:45   Logging conflicted queries on deadlocks ITAGAKI Takahiro
• 08:09   CREATE TABLE, load and freezing Pavan Deolasee
• 08:35   Re: CREATE TABLE, load and freezing Florian G. Pflug
• 08:45   Re: Varlena Type Creation Dimitri Fontaine
• 08:56   Re: CREATE TABLE, load and freezing ITAGAKI Takahiro
• 09:01   Re: CREATE TABLE, load and freezing Pavan Deolasee
• 09:17   Re: CREATE TABLE, load and freezing Pavan Deolasee
• 09:20   Re: CREATE TABLE, load and freezing Heikki Linnakangas
• 09:25   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Jochem van Dieten
• 09:29   Re: Proposal: wildcards in pg_service.conf Albe Laurenz
• 11:22   Re: OSSP can be used in the windows environment now! Magnus Hagander
• 11:34   Re: OSSP can be used in the windows environment now! Dave Page
• 11:40   Re: Logging conflicted queries on deadlocks Alvaro Herrera
• 11:52   Silly Newbie question Aaron Spiteri
• 12:34   Re: Logging conflicted queries on deadlocks Alvaro Herrera
• 12:45   Re: Buildfarm member gypsy_moth seems not to like alignment patch Jorgen Austvik - Sun Norway
• 12:49   Re: Buildfarm member gypsy_moth seems not to like alignment patch Jorgen Austvik - Sun Norway
• 12:51   Re: CREATE TABLE, load and freezing Florian Pflug
• 13:21   Re: Silly Newbie question Andrew Dunstan
• 13:40   Re: Producer/Consumer Issues in the COPY across network Martijn van Oosterhout
• 15:58   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Josh Berkus
• 16:46   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Andrew Sullivan
• 17:28   Google SoC 2008? Joey K.
• 18:06   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Zeugswetter Andreas ADI SD
• 18:27   Re: OSSP can be used in the windows environment now! Hiroshi Saito
• 18:37   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Kenneth Marshall
• 20:37   Re: Producer/Consumer Issues in the COPY across network Simon Riggs
• 20:39   Re: Google SoC 2008? Josh Berkus
• 20:45   Need Mentors for Google Summer of Code! Josh Berkus
• 21:42   Re: CREATE TABLE, load and freezing Kevin Grittner
• 21:53   Re: Google SoC 2008? Kevin Grittner
• 22:07   Re: Need Mentors for Google Summer of Code! Jonah H. Harris
• 22:24   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x James Mansion
• 22:46   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Mark Mielke
• 23:04   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x James Mansion
• 23:09   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Sam Mason
• 23:46   Re: Proposal: wildcards in pg_service.conf Dawid Kuroczko

29 February 2008

• 00:54   "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables John Smith
• 02:23   A couple of PG schedule reminders Tom Lane
• 02:26   Re: Batch update of indexes on data loading Tom Lane
• 02:45   Re: CREATE TABLE, load and freezing Tom Lane
• 02:56   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Tom Lane
• 03:03   Re: OSSP can be used in the windows environment now! Tom Lane
• 03:06   Re: CREATE TABLE, load and freezing Pavan Deolasee
• 03:07   Re: Silly Newbie question Tom Lane
• 03:14   Re: Silly Newbie question Tom Lane
• 03:29   Re: Silly Newbie question Andrew Dunstan
• 03:40   Re: Batch update of indexes on data loading Markus Bertheau
• 04:06   Re: Batch update of indexes on data loading Tom Lane
• 04:26   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Mark Mielke
• 04:40   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Tom Dunstan
• 05:09   Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x Tom Lane
• 05:18   Re: Batch update of indexes on data loading ITAGAKI Takahiro
• 05:38   Re: Batch update of indexes on data loading Tom Lane
• 09:03   Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables Heikki Linnakangas
• 10:28   Re: CREATE TABLE, load and freezing Simon Riggs
• 10:30   Read-ahead and parallelism in redo recovery Pavan Deolasee
• 12:08   Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables Heikki Linnakangas
• 12:10   Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables Gurjeet Singh
• 12:57   Why we panic in pglz_decompress Zdenek Kotala
• 13:09   Re: Why we panic in pglz_decompress Alvaro Herrera
• 13:17   Re: Read-ahead and parallelism in redo recovery Florian Weimer
• 13:49   Re: Read-ahead and parallelism in redo recovery Florian G. Pflug
• 14:09   Re: Why we panic in pglz_decompress Zdenek Kotala
• 14:52   Re: Why we panic in pglz_decompress Tom Lane
• 15:08   Re: Read-ahead and parallelism in redo recovery Tom Lane
• 15:26   Re: [BUGS] bug or not bug, xmlvalidate(xml, text) can read and show one line from file Tom Lane
• 15:26   Re: Why we panic in pglz_decompress Zdenek Kotala
• 15:42   request feature: alter view add column (or something like) Olivier Thauvin
• 16:28   creating new aggregate function Justin
• 16:37   Re: creating new aggregate function Sam Mason
• 16:44   Re: Read-ahead and parallelism in redo recovery Simon Riggs
• 16:49   Re: Buildfarm member gypsy_moth seems not to like alignment patch Tom Lane
• 18:30   Re: [BUGS] bug or not bug, xmlvalidate(xml, text) can read and show one line from file Peter Eisentraut
• 18:32   Re: creating new aggregate function Webb Sprague
• 18:42   Re: [BUGS] bug or not bug, xmlvalidate(xml, text) can read and show one line from file Alvaro Herrera
• 18:48   Re: [BUGS] bug or not bug, xmlvalidate(xml, text) can read and show one line from file Tom Lane
• 18:59   Re: Read-ahead and parallelism in redo recovery Decibel!
• 19:44   Re: Read-ahead and parallelism in redo recovery Heikki Linnakangas
• 19:47   Re: Read-ahead and parallelism in redo recovery Tom Lane
• 19:59   Re: Read-ahead and parallelism in redo recovery Aidan Van Dyk
• 20:37   Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables Heikki Linnakangas
• 20:42   Re: pg_dump additional options for performance Decibel!
• 21:30   Re: Read-ahead and parallelism in redo recovery Gregory Stark