Mailing lists [pgsql-hackers]

20 February 2012

• 00:40   Re: Future of our regular expression code Tom Lane
• 00:42   Re: leakproof Tom Lane
• 01:13   Re: Future of our regular expression code Billy Earney
• 01:16   Re: Future of our regular expression code Stephen Frost
• 01:20   Re: leakproof Don Baccus
• 02:18   Re: leakproof Greg Stark
• 02:25   Re: leakproof Tom Lane
• 02:29   Re: Future of our regular expression code Greg Stark
• 02:29   Re: Potential reference miscounts and segfaults in plpython.c Tom Lane
• 02:38   Re: Future of our regular expression code Stephen Frost
• 02:43   Re: Future of our regular expression code Tom Lane
• 03:10   Re: wal_buffers Fujii Masao
• 03:12   Re: Initial 9.2 pgbench write results Greg Smith
• 03:18   Re: Initial 9.2 pgbench write results Greg Smith
• 03:26   Re: wal_buffers Greg Smith
• 04:04   Re: Future of our regular expression code Greg Smith
• 04:37   Re: leakproof Don Baccus
• 05:09   Re: Future of our regular expression code Jay Levitt
• 05:17   Re: leakproof Robert Haas
• 05:27   Re: Initial 9.2 pgbench write results Robert Haas
• 06:34   Re: Proposal: XML helper functions Larry
• 06:34   Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock) Amit Kapila
• 06:49   Re: Displaying accumulated autovacuum cost Fujii Masao
• 07:45   Re: Incorrect behaviour when using a GiST index on points Alexander Korotkov
• 07:52   Re: Google Summer of Code? Call for mentors. Alexander Korotkov
• 07:55   Re: Bugs/slowness inserting and indexing cubes Alexander Korotkov
• 07:56   Re: leakproof Yeb Havinga
• 07:57   Re: leakproof Albe Laurenz
• 07:59   Re: wal_buffers Simon Riggs
• 08:01   Re: Google Summer of Code? Call for mentors. Jehan-Guillaume (ioguix) de Rorthais
• 08:09   Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock) Fujii Masao
• 08:18   Re: pgsql_fdw, FDW for PostgreSQL server Albe Laurenz
• 08:19   Re: Qual evaluation cost estimates for GIN indexes Marc Mamin
• 08:19   Re: 16-bit page checksums for 9.2 Simon Riggs
• 09:06   Re: Potential reference miscounts and segfaults in plpython.c Jan Urbański
• 11:30   array_to_json re-encodes ARRAY of json type Itagaki Takahiro
• 12:35   Re: Potential reference miscounts and segfaults in plpython.c Robert Haas
• 12:57   Re: 16-bit page checksums for 9.2 Robert Haas
• 13:01   Re: Displaying accumulated autovacuum cost Robert Haas
• 13:01   Re: array_to_json re-encodes ARRAY of json type Andrew Dunstan
• 13:25   Re: Qual evaluation cost estimates for GIN indexes ktm@rice.edu
• 13:32   Re: Qual evaluation cost estimates for GIN indexes Marc Mamin
• 13:35   Re: [v9.2] Add GUC sepgsql.client_label Yeb Havinga
• 13:57   Re: pgsql_fdw, FDW for PostgreSQL server Kevin Grittner
• 14:23   Re: Incorrect behaviour when using a GiST index on points Tom Lane
• 14:32   Re: REASSIGN OWNED lacks support for FDWs Robert Haas
• 14:38   Re: REASSIGN OWNED lacks support for FDWs Tom Lane
• 14:52   Re: pgsql_fdw, FDW for PostgreSQL server Albe Laurenz
• 14:58   Re: pgsql_fdw, FDW for PostgreSQL server Kevin Grittner
• 16:34   Re: Incorrect behaviour when using a GiST index on points Alexander Korotkov
• 16:54   Re: 16-bit page checksums for 9.2 Josh Berkus
• 17:22   Re: 16-bit page checksums for 9.2 Robert Haas
• 18:23   Re: wal_buffers Robert Haas
• 20:25   Re: Future of our regular expression code Billy Earney
• 20:35   Re: Future of our regular expression code Tom Lane
• 20:59   Re: Future of our regular expression code Billy Earney
• 21:21   Re: Future of our regular expression code Tom Lane
• 21:49   Re: 16-bit page checksums for 9.2 Josh Berkus
• 22:08   Re: pgsql_fdw, FDW for PostgreSQL server Shigeru Hanada
• 22:09   Re: 16-bit page checksums for 9.2 Bruce Momjian
• 22:14   Re: 16-bit page checksums for 9.2 Simon Riggs
• 22:16   Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation) Peter Geoghegan
• 22:24   Re: 16-bit page checksums for 9.2 Simon Riggs