Mailing lists [pgsql-hackers]

22 November 2011

• 00:34   explain analyze query execution time Rudyar
• 00:54   Re: EXPLAIN (plan off, rewrite off) for benchmarking Tom Lane
• 01:15   Re: btvacuumpage useless "orig_blkno" Tom Lane
• 01:24   Re: Removing postgres -f command line option Tom Lane
• 01:33   Re: [COMMITTERS] pgsql: Avoid marking buffer dirty when VACUUM has no work to do. Tom Lane
• 01:42   Re: Removing postgres -f command line option Bruce Momjian
• 02:13   Rename a database that has connections Mark Kirkwood
• 02:18   Re: strange nbtree corruption report Noah Misch
• 02:38   Re: Rename a database that has connections Bruce Momjian
• 02:41   Re: Rename a database that has connections Tom Lane
• 02:43   Re: strange nbtree corruption report Tom Lane
• 03:03   Re: Rename a database that has connections Mark Kirkwood
• 03:05   Re: Rename a database that has connections Bruce Momjian
• 03:14   Re: strange nbtree corruption report Tom Lane
• 03:17   Re: strange nbtree corruption report Tom Lane
• 03:20   Re: explain analyze query execution time Jeff Janes
• 03:24   Re: Rename a database that has connections Mark Kirkwood
• 03:30   Re: Rename a database that has connections Mark Kirkwood
• 03:56   dblink: enable parameters Pavel Stehule
• 04:06   Re: Rename a database that has connections Mark Kirkwood
• 04:59   Re: explain analyze query execution time Kevin Grittner
• 06:50   Re: Singleton range constructors versus functional coercion notation Dean Rasheed
• 08:32   Re: [GENERAL] VACUUM touching file but not updating relation Simon Riggs
• 08:37   Re: [COMMITTERS] pgsql: Avoid marking buffer dirty when VACUUM has no work to do. Simon Riggs
• 09:59   Re: Allow substitute allocators for PGresult. Kyotaro HORIGUCHI
• 10:09   Re: dblink: enable parameters Heikki Linnakangas
• 11:22   Re: dblink: enable parameters Itagaki Takahiro
• 11:53   Re: explain analyze query execution time Rudyar
• 12:14   Review: CHECK FUNCTION statement Albe Laurenz
• 12:26   Re: explain analyze query execution time Kevin Grittner
• 12:41   Re: explain analyze query execution time Rudyar
• 13:05   Re: Review: CHECK FUNCTION statement Pavel Stehule
• 13:07   Re: Singleton range constructors versus functional coercion notation Robert Haas
• 13:36   Re: EXPLAIN (plan off, rewrite off) for benchmarking Robert Haas
• 14:18   Re: EXPLAIN (plan off, rewrite off) for benchmarking Tom Lane
• 15:53   Re: Singleton range constructors versus functional coercion notation Jeff Davis
• 16:37   Re: Storing hot members of PGPROC out of the band Robert Haas
• 16:37   Re: strange nbtree corruption report Alvaro Herrera
• 17:01   Re: Singleton range constructors versus functional coercion notation Tom Lane
• 17:05   Re: testing ProcArrayLock patches Pavan Deolasee
• 18:04   Re: testing ProcArrayLock patches Kevin Grittner
• 18:22   Re: vpath builds and verbose error messages Peter Eisentraut
• 18:39   WIP: index support for regexp search Alexander Korotkov
• 18:40   Re: vpath builds and verbose error messages Alvaro Herrera
• 19:02   pg_upgrade relation OID mismatches Peter Eisentraut
• 19:23   Not HOT enough Simon Riggs
• 19:42   Re: pg_upgrade relation OID mismatches Bruce Momjian
• 20:17   Re: Review for "Add permission check on SELECT INTO" Robert Haas
• 20:22   Re: Not HOT enough Robert Haas
• 20:47   Optimize postgres protocol for fixed size arrays Mikko Tiihonen
• 20:57   Re: pg_upgrade relation OID mismatches Peter Eisentraut
• 20:58   Re: Optimize postgres protocol for fixed size arrays ktm@rice.edu
• 21:36   Re: FlexLocks Kevin Grittner
• 21:46   Re: Optimize postgres protocol for fixed size arrays Merlin Moncure
• 22:29   Re: pg_upgrade relation OID mismatches Bruce Momjian
• 22:38   Permissions checks for range-type support functions Tom Lane
• 22:40   Re: Not HOT enough Simon Riggs
• 22:42   Re: [JDBC] Optimize postgres protocol for fixed size arrays Oliver Jowett
• 22:52   Re: [JDBC] Optimize postgres protocol for fixed size arrays Tom Lane
• 23:07   Re: vpath builds and verbose error messages Tom Lane
• 23:32   Re: Not HOT enough Simon Riggs