pgsql-hackers since 2011-11-22 00:00

The PostgreSQL developers team lives here. Discussion of current development issues, problems and bugs, and proposed new features. If your question cannot be answered by people in the other lists, and it is likely that only a developer will know the answer, you may re-post your question in this list. You must try elsewhere first!

Search the Archives

(enter a message-id to go directly to that message)

Advanced Search

Browse Archives

Prev | Next

Nov. 22, 2011

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