Mailing lists [pgsql-hackers]

21 September 2011

• 00:20   Re: EXPLAIN and nfiltered, take two Tom Lane
• 00:24   Re: WIP: Collecting statistics on CSV file data David Fetter
• 00:30   Isolation tests still falling over routinely Tom Lane
• 01:01   Re: WIP: Collecting statistics on CSV file data Alvaro Herrera
• 01:05   Re: Inlining comparators as a performance optimisation karavelov@mail.bg
• 01:51   Re: Isolation tests still falling over routinely Kevin Grittner
• 02:04   Re: Isolation tests still falling over routinely Alvaro Herrera
• 02:18   Re: EXPLAIN and nfiltered, take two Robert Haas
• 02:50   Re: Online base backup from the hot-standby Fujii Masao
• 03:28   Re: Is there really no interest in SQL Standard? Peter Eisentraut
• 03:42   Re: Isolation tests still falling over routinely Tom Lane
• 03:52   Re: WIP: Join push-down for foreign tables Michael Paquier
• 04:01   Re: Back-branch releases upcoming this week Peter Eisentraut
• 05:13   Re: Online base backup from the hot-standby Magnus Hagander
• 06:11   Re: WIP: Join push-down for foreign tables Shigeru Hanada
• 06:24   Re: Online base backup from the hot-standby Fujii Masao
• 06:51   Re: Inlining comparators as a performance optimisation Heikki Linnakangas
• 06:56   Re: Inlining comparators as a performance optimisation Simon Riggs
• 07:02   Re: Inlining comparators as a performance optimisation Simon Riggs
• 07:08   Re: Inlining comparators as a performance optimisation Heikki Linnakangas
• 07:20   Re: WIP: Join push-down for foreign tables Michael Paquier
• 07:22   Re: Range Types - typo + NULL string constructor Jeff Davis
• 07:28   Re: Range Types - typo + NULL string constructor Jeff Davis
• 07:38   Re: Inlining comparators as a performance optimisation Peter Geoghegan
• 07:43   Shared sequence-like objects in PostgreSQL Vlad Arkhipov
• 08:34   Re: Online base backup from the hot-standby Magnus Hagander
• 09:13   Re: Improve lseek scalability v3 Marco Stornelli
• 09:13   Re: Inlining comparators as a performance optimisation Amit Kapila
• 09:13   [PATCH] POC: inline int4 comparison in tuplesort Dan McGee
• 11:24   Re: Range Types - typo + NULL string constructor Florian Pflug
• 12:00   Re: Range Types - typo + NULL string constructor Robert Haas
• 12:34   Re: Shared sequence-like objects in PostgreSQL Greg Stark
• 12:41   Re: Range Types - typo + NULL string constructor Florian Pflug
• 12:47   Re: Range Types - typo + NULL string constructor Robert Haas
• 12:48   Re: Inlining comparators as a performance optimisation Greg Stark
• 13:34   Re: Inlining comparators as a performance optimisation Robert Haas
• 14:21   Re: Inlining comparators as a performance optimisation Peter Geoghegan
• 14:31   Re: Inlining comparators as a performance optimisation Heikki Linnakangas
• 14:41   Re: Range Types - typo + NULL string constructor Tom Lane
• 14:50   Re: Inlining comparators as a performance optimisation Tom Lane
• 14:54   Hot Backup with rsync fails at pg_clog if under load Linas Virbalas
• 15:03   Re: Inlining comparators as a performance optimisation Andrew Dunstan
• 15:15   sequence locking Andres Freund
• 15:20   Re: Range Types - typo + NULL string constructor Florian Pflug
• 15:23   Re: Inlining comparators as a performance optimisation Tom Lane
• 15:34   Re: Is there really no interest in SQL Standard? Susanne Ebrecht
• 15:43   Re: Inlining comparators as a performance optimisation Peter Geoghegan
• 15:47   Re: Inlining comparators as a performance optimisation Tom Lane
• 15:57   Re: Inlining comparators as a performance optimisation Heikki Linnakangas
• 16:05   Re: Inlining comparators as a performance optimisation Greg Stark
• 16:13   Re: Inlining comparators as a performance optimisation Tom Lane
• 16:13   Re: Inlining comparators as a performance optimisation Heikki Linnakangas
• 16:19   DECLARE CURSOR must not contain data-modifying statements in WITH Andres Freund
• 16:23   Re: Inlining comparators as a performance optimisation Tom Lane
• 16:23   Re: Hot Backup with rsync fails at pg_clog if under load Euler Taveira de Oliveira
• 16:28   Re: Inlining comparators as a performance optimisation Tom Lane
• 16:29   unaccent contrib Daniel Vázquez
• 16:34   Re: Hot Backup with rsync fails at pg_clog if under load Florian Pflug
• 16:36   Re: Inlining comparators as a performance optimisation Greg Stark
• 16:49   Re: Is there really no interest in SQL Standard? Alvaro Herrera
• 16:50   Re: Is there really no interest in SQL Standard? Dave Page
• 16:51   Re: sequence locking Kevin Grittner
• 16:52   Remastering using streaming only replication? Josh Berkus
• 16:54   Re: sequence locking Merlin Moncure
• 16:55   Re: unite recovery.conf and postgresql.conf Josh Berkus
• 16:57   Re: unite recovery.conf and postgresql.conf Robert Haas
• 16:59   Re: Range Types - typo + NULL string constructor Jeff Davis
• 17:01   Re: Range Types - typo + NULL string constructor Jeff Davis
• 17:03   Re: sequence locking Kevin Grittner
• 17:04   Re: unite recovery.conf and postgresql.conf Josh Berkus
• 17:07   Re: unite recovery.conf and postgresql.conf Robert Haas
• 17:08   Re: unite recovery.conf and postgresql.conf Josh Berkus
• 17:11   Re: [PERFORM] Constraint exclusion on UNION ALL subqueries with WHERE conditions Tom Lane
• 17:13   Re: unite recovery.conf and postgresql.conf Robert Haas
• 17:15   Re: sequence locking Andres Freund
• 17:23   Re: Hot Backup with rsync fails at pg_clog if under load Robert Haas
• 17:25   Re: sequence locking Tom Lane
• 17:35   Re: unite recovery.conf and postgresql.conf Aidan Van Dyk
• 17:39   Re: unite recovery.conf and postgresql.conf Aidan Van Dyk
• 17:41   Re: sequence locking Andres Freund
• 17:55   Re: unaccent contrib Euler Taveira de Oliveira
• 18:03   HeapTupleSatisfiesToast not setting XMIN_COMMITTED? Alvaro Herrera
• 18:03   Re: sequence locking Kevin Grittner
• 18:09   Re: sequence locking Merlin Moncure
• 18:27   Re: unaccent contrib Daniel Vázquez
• 18:33   Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) Robert Haas
• 18:48   Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) Kevin Grittner
• 19:02   Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED? Merlin Moncure
• 19:08   Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) Robert Haas
• 19:14   Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED? Alvaro Herrera
• 19:21   Re: Inlining comparators as a performance optimisation Simon Riggs
• 19:25   Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED? Merlin Moncure
• 19:38   Re: WIP: SP-GiST, Space-Partitioned GiST Heikki Linnakangas
• 19:40   Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) Kevin Grittner
• 20:02   Re: unaccent contrib Euler Taveira de Oliveira
• 20:02   Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED? Tom Lane
• 20:05   Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED? Tom Lane
• 20:20   Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) Gurjeet Singh
• 20:22   Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) Robert Haas
• 20:39   Re: unaccent contrib Devrim GÜNDÜZ
• 20:41   Re: unaccent contrib Tom Lane
• 20:41   Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) Robert Haas
• 21:08   Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) Kevin Grittner
• 21:49   Re: EXPLAIN and nfiltered, take two Tom Lane
• 21:56   Re: Double sorting split patch Alexander Korotkov
• 23:52   citext operator precedence fix Josh Berkus