Mailing lists [pgsql-hackers]

2 February 2013

• 00:03   Re: some psql table output flaws Erik Rijkers
• 00:15   Re: GetOldestXmin going backwards is dangerous after all Robert Haas
• 00:34   Re: Re: [PATCH 1/5] Centralize Assert* macros into c.h so its common between backend/frontend Alvaro Herrera
• 00:59   Re: autovacuum not prioritising for-wraparound tables Robert Haas
• 01:05   Re: autovacuum not prioritising for-wraparound tables Jeff Janes
• 01:08   Re: json api WIP patch Robert Haas
• 01:13   Re: cannot move relocatable extension out of pg_catalog schema Peter Eisentraut
• 01:16   Re: obsolete code Peter Eisentraut
• 01:34   Re: autovacuum not prioritising for-wraparound tables Andres Freund
• 01:39   Re: json api WIP patch Daniel Farina
• 01:43   Re: autovacuum not prioritising for-wraparound tables Christopher Browne
• 01:56   Re: proposal - assign result of query to psql variable Tom Lane
• 02:03   Re: json api WIP patch Tom Lane
• 02:08   Re: autovacuum not prioritising for-wraparound tables Tom Lane
• 02:09   Re: autovacuum not prioritising for-wraparound tables Jeff Janes
• 02:17   Cascading replica waits for write on master to come up Josh Berkus
• 02:40   issues with range types, btree_gist and constraints Tomas Vondra
• 02:56   Re: GetOldestXmin going backwards is dangerous after all Tom Lane
• 03:24   Re: GetOldestXmin going backwards is dangerous after all Tom Lane
• 07:49   Re: autovacuum not prioritising for-wraparound tables Jeff Janes
• 12:24   proposal 9.4 plpgsql: allows access to call stack from GET DIAGNOSTICS statement Pavel Stehule
• 13:06   Using indexes for partial index builds Paul Norman
• 13:30   Re: proposal - assign result of query to psql variable Pavel Stehule
• 14:01   Re: GetOldestXmin going backwards is dangerous after all Simon Riggs
• 14:07   Re: GetOldestXmin going backwards is dangerous after all Simon Riggs
• 14:25   Re: proposal - assign result of query to psql variable Shigeru Hanada
• 16:25   Re: autovacuum not prioritising for-wraparound tables Andres Freund
• 16:41   Re: autovacuum not prioritising for-wraparound tables Andres Freund
• 17:24   Re: GetOldestXmin going backwards is dangerous after all Andres Freund
• 17:49   Re: proposal - assign result of query to psql variable Pavel Stehule
• 17:51   Re: COPY FREEZE has no warning Noah Misch
• 18:13   Re: COPY FREEZE has no warning Bruce Momjian
• 18:20   Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker) Vlad Bailescu
• 18:23   Re: GetOldestXmin going backwards is dangerous after all Robert Haas
• 18:34   Re: GetOldestXmin going backwards is dangerous after all Robert Haas
• 18:38   Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block Robert Haas
• 18:43   Re: autovacuum not prioritising for-wraparound tables Robert Haas
• 19:25   Re: autovacuum not prioritising for-wraparound tables Robert Haas
• 20:09   Re: COPY FREEZE has no warning Tom Lane
• 20:39   Re: proposal - assign result of query to psql variable Tom Lane
• 20:56   Re: COPY FREEZE has no warning Bruce Momjian
• 21:33   Re: GetOldestXmin going backwards is dangerous after all Simon Riggs
• 21:34   Re: GetOldestXmin going backwards is dangerous after all Simon Riggs
• 21:35   Re: GetOldestXmin going backwards is dangerous after all Simon Riggs
• 21:38   Re: GetOldestXmin going backwards is dangerous after all Andres Freund
• 21:41   Re: Cascading replication: should we detect/prevent cycles? Robert Haas
• 21:49   Re: autovacuum not prioritising for-wraparound tables Andres Freund
• 22:27   Re: COPY FREEZE has no warning Noah Misch
• 22:54   Re: autovacuum not prioritising for-wraparound tables Robert Haas
• 23:11   Re: GetOldestXmin going backwards is dangerous after all Simon Riggs
• 23:39   Re: proposal - assign result of query to psql variable Pavel Stehule
• 23:43   Re: PL/Python result object str handler Steve Singer