Mailing lists [pgsql-performance]

1 June 2009

• 03:29   Re: degenerate performance on one server of 3 Craig Ringer
• 03:40   Re: degenerate performance on one server of 3 Tom Lane
• 04:13   Re: degenerate performance on one server of 3 Erik Aronesty
• 05:26   Vacuuming technique doubt S Arvind
• 11:05   Postgresql cache (memory) performance + how to warm up the cache Shaul Dar
• 12:45   Re: Vacuuming technique doubt David Rees
• 13:18   Re: Postgresql cache (memory) performance + how to warm up the cache Greg Smith
• 14:06   Re: degenerate performance on one server of 3 Tom Lane
• 15:34   Re: Vacuuming technique doubt Greg Smith
• 15:46   Using index for bitwise operations? Shaul Dar
• 16:08   Best way to load test a postgresql server Peter Sheats
• 16:14   Very inefficient query plan with disjunction in WHERE clause Koen Martens
• 16:18   Re: Using index for bitwise operations? Richard Huxton
• 16:19   Re: Using index for bitwise operations? Tom Lane
• 16:27   Re: Very inefficient query plan with disjunction in WHERE clause Віталій Тимчишин
• 16:27   Re: Best way to load test a postgresql server Alan McKay
• 18:02   Re: Vacuuming technique doubt S Arvind
• 18:14   Re: Unexpected query plan results Anne Rosset
• 19:19   Re: Scalability in postgres Scott Carey
• 20:24   Re: Unexpected query plan results Robert Haas
• 20:53   Re: Unexpected query plan results Anne Rosset
• 21:07   Re: Unexpected query plan results Dave Dutcher
• 21:10   Re: Unexpected query plan results Anne Rosset
• 22:58   Re: Unexpected query plan results Robert Haas

2 June 2009

• 00:35   Re: Vacuuming technique doubt Kevin Grittner
• 00:41   Re: Vacuuming technique doubt Robert Haas
• 00:42   Re: Scalability in postgres Ron Mayer
• 04:23   Re: Scalability in postgres Greg Smith
• 09:28   Re: Best way to load test a postgresql server Dimitri Fontaine
• 10:26   Re: Unexpected query plan results Віталій Тимчишин
• 11:48   Re: Unexpected query plan results Robert Haas
• 12:30   Re: Very inefficient query plan with disjunction in WHERE clause Matthew Wakeling
• 12:47   Re: Very inefficient query plan with disjunction in WHERE clause Matthew Wakeling
• 12:48   Re: Using index for bitwise operations? Matthew Wakeling
• 13:02   Re: Best way to load test a postgresql server Kenneth Cox
• 13:31   Re: Best way to load test a postgresql server Shaul Dar
• 15:16   Re: Unexpected query plan results Anne Rosset
• 15:41   Re: Unexpected query plan results Robert Haas

3 June 2009

• 09:26   Re: Best way to load test a postgresql server Dimitri Fontaine
• 10:30   Re: Scalability in postgres James Mansion
• 11:11   Re: Best way to load test a postgresql server Shaul Dar
• 13:09   Re: Best way to load test a postgresql server Kenneth Cox
• 14:09   Re: Scalability in postgres Kevin Grittner
• 15:50   poor performing plan from analyze vs. fast default plan pre-analyze on new database Davin Potts
• 16:07   Re: poor performing plan from analyze vs. fast default plan pre-analyze on new database Grzegorz Jaśkiewicz
• 16:28   Re: poor performing plan from analyze vs. fast default plan pre-analyze on new database Tom Lane
• 17:08   Re: poor performing plan from analyze vs. fast default plan pre-analyze on new database Scott Carey
• 17:27   Re: Scalability in postgres Dimitri
• 17:45   Re: Scalability in postgres Kevin Grittner
• 18:13   Re: Scalability in postgres Scott Carey
• 18:16   Re: Scalability in postgres Dimitri
• 18:39   Re: Scalability in postgres Robert Haas
• 19:30   Re: degenerate performance on one server of 3 Erik Aronesty
• 21:09   Re: Scalability in postgres Scott Carey
• 21:15   Re: degenerate performance on one server of 3 Tom Lane
• 21:34   Pointers needed on optimizing slow SQL statements Janine Sisk
• 21:43   Re: Pointers needed on optimizing slow SQL statements Tom Lane
• 22:04   Re: Pointers needed on optimizing slow SQL statements Janine Sisk
• 23:01   Re: Best way to load test a postgresql server Greg Smith

4 June 2009

• 01:21   Re: Pointers needed on optimizing slow SQL statements Robert Haas
• 02:09   Query plan issues - volatile tables Brian Herlihy
• 02:32   Re: Pointers needed on optimizing slow SQL statements Janine Sisk
• 02:35   Re: degenerate performance on one server of 3 Reid Thompson
• 05:31   Re: Pointers needed on optimizing slow SQL statements Scott Marlowe
• 08:22   Re: Scalability in postgres Marc Cousin
• 10:58   Re: Scalability in postgres Robert Haas
• 11:31   Re: degenerate performance on one server of 3 Erik Aronesty
• 13:16   Re: degenerate performance on one server of 3 Robert Haas
• 16:33   GiST index performance Matthew Wakeling
• 16:36   Re: Query plan issues - volatile tables Craig James
• 17:34   Re: degenerate performance on one server of 3 Scott Carey
• 18:04   Re: Scalability in postgres Scott Carey
• 18:10   Re: degenerate performance on one server of 3 Scott Carey
• 18:29   Re: Scalability in postgres Robert Haas
• 19:43   Re: Pointers needed on optimizing slow SQL statements Josh Berkus
• 21:25   Re: Scalability in postgres James Mansion
• 22:08   Re: Scalability in postgres Kevin Grittner
• 22:33   Re: Scalability in postgres Kevin Grittner
• 23:03   Re: Scalability in postgres Mark Mielke

5 June 2009

• 00:52   Re: Scalability in postgres david@lang.hm
• 00:54   Re: Scalability in postgres Scott Carey
• 01:04   Re: Scalability in postgres david@lang.hm
• 02:07   Re: Scalability in postgres Robert Haas
• 03:36   Re: Scalability in postgres Mark Mielke
• 04:13   Re: Scalability in postgres Greg Smith
• 04:29   Re: Scalability in postgres david@lang.hm
• 04:34   Re: Scalability in postgres david@lang.hm
• 05:55   Re: Scalability in postgres Mark Mielke
• 10:06   Why is my stats collector so busy? Laszlo Nagy
• 13:38   Re: Why is my stats collector so busy? Bruce Momjian
• 13:47   Re: Why is my stats collector so busy? Tom Lane
• 13:52   Re: Why is my stats collector so busy? Merlin Moncure
• 14:29   Re: Scalability in postgres Kevin Grittner
• 14:42   Re: Scalability in postgres Kevin Grittner
• 15:19   Re: Scalability in postgres Robert Haas
• 16:07   Re: Scalability in postgres Craig James
• 17:02   Re: Scalability in postgres Greg Smith
• 17:15   Re: Scalability in postgres Greg Smith
• 19:01   Re: Why is my stats collector so busy? Robert Schnabel
• 19:42   Re: GiST index performance Robert Haas
• 19:48   Re: Scalability in postgres Robert Haas
• 22:00   Re: Bad Plan for Questionnaire-Type Query David Blewett
• 23:32   Re: Bad Plan for Questionnaire-Type Query Josh Berkus

6 June 2009

• 00:29   Re: Bad Plan for Questionnaire-Type Query David Blewett
• 01:50   Re: degenerate performance on one server of 3 Erik Aronesty
• 02:02   Re: Bad Plan for Questionnaire-Type Query Robert Haas
• 02:17   Re: degenerate performance on one server of 3 Robert Haas
• 08:47   Re: Pointers needed on optimizing slow SQL statements Simon Riggs
• 22:36   Vacuum ALL FULL S Arvind
• 22:40   Re: Vacuum ALL FULL S Arvind
• 22:45   Re: Vacuum ALL FULL Tom Lane
• 23:00   Re: Vacuum ALL FULL S Arvind
• 23:00   Re: Vacuum ALL FULL S Arvind
• 23:02   Re: Vacuum ALL FULL Tom Lane
• 23:10   Re: Vacuum ALL FULL S Arvind
• 23:12   Re: Vacuum ALL FULL Tom Lane
• 23:29   Re: Vacuum ALL FULL S Arvind
• 23:42   Postgres installation for Performance S Arvind

7 June 2009

• 18:28   Re: Pointers needed on optimizing slow SQL statements Dimitri Fontaine
• 20:28   Re: Pointers needed on optimizing slow SQL statements Robert Haas

8 June 2009

• 11:09   Re: Why is my stats collector so busy? Laszlo Nagy
• 19:37   Re: Problems with autovacuum Alvaro Herrera
• 20:17   Re: Problems with autovacuum Tom Lane

9 June 2009

• 06:58   Re: Pointers needed on optimizing slow SQL statements Віталій Тимчишин
• 08:33   Re: Pointers needed on optimizing slow SQL statements Dimitri Fontaine
• 12:50   Re: Best way to load test a postgresql server Shaul Dar
• 13:53   Re: Best way to load test a postgresql server Tom Lane
• 15:51   Re: Problems with autovacuum Alvaro Herrera
• 16:42   Re: Problems with autovacuum Alvaro Herrera
• 16:43   Re: Problems with autovacuum Tom Lane
• 23:18   Looking for installations with a large number of concurrent users David Kerr

10 June 2009

• 09:10   Re: Why is my stats collector so busy? Laszlo Nagy
• 11:23   Re: Hosted servers with good DB disk performance? Markus Wanner
• 11:46   Re: GiST index performance Matthew Wakeling
• 13:12   Censorship Matthew Wakeling
• 13:21   Re: Censorship Guillaume Cottenceau
• 13:24   Re: Censorship Matthew Wakeling
• 13:26   Re: Censorship Gurjeet Singh
• 13:39   Re: Censorship Matthew Wakeling
• 13:41   Re: Censorship Scott Mead
• 13:48   Re: Censorship Matthew Wakeling
• 14:03   Re: Censorship Tom Lane
• 14:44   Explaining an EXPLAIN. Matthew Wakeling
• 14:44   EXPLAIN understanding? (restarted from Censorship) Richard Huxton
• 14:47   Re: EXPLAIN understanding? (restarted from Censorship) Richard Huxton
• 14:59   Re: Explaining an EXPLAIN. Tom Lane
• 15:02   Re: Explaining an EXPLAIN. Matthew Wakeling
• 16:40   Re: Looking for installations with a large number of concurrent users Kevin Grittner
• 16:51   Re: GiST index performance Tom Lane
• 17:07   Re: Why is my stats collector so busy? Tom Lane
• 19:57   Re: Looking for installations with a large number of concurrent users David Kerr

11 June 2009

• 12:16   Re: Hosted servers with good DB disk performance? Dimitri Fontaine
• 12:38   Re: GiST index performance Matthew Wakeling
• 13:12   Postgres replication: dump/restore, PITR, Slony,...? Shaul Dar
• 13:27   Re: GiST index performance Tom Lane
• 14:34   Re: Postgres replication: dump/restore, PITR, Slony,...? Dimitri Fontaine
• 15:07   Re: GiST index performance Matthew Wakeling
• 15:39   Re: GiST index performance Tom Lane
• 16:23   Re: Postgres replication: dump/restore, PITR, Slony,...? Joshua D. Drake
• 16:30   Re: Postgres replication: dump/restore, PITR, Slony,...? Greg Sabino Mullane
• 16:32   Re: Postgres replication: dump/restore, PITR, Slony,...? Joshua D. Drake
• 16:42   Re: GiST index performance Matthew Wakeling
• 16:44   Re: GiST index performance Matthew Wakeling
• 17:23   Re: GiST index performance Matthew Wakeling
• 17:34   Re: GiST index performance Tom Lane
• 21:30   Re: Best way to load test a postgresql server Erik Aronesty

12 June 2009

• 11:27   Re: Postgres replication: dump/restore, PITR, Slony,...? Shaul Dar
• 15:20   Re: GiST index performance Adam Gundy
• 19:12   Re: Postgres replication: dump/restore, PITR, Slony,...? Greg Sabino Mullane
• 19:52   what server stats to track / monitor ? Alan McKay
• 20:35   Re: what server stats to track / monitor ? Joshua Tolley
• 20:40   Re: what server stats to track / monitor ? Alan McKay
• 20:41   Re: what server stats to track / monitor ? Alan McKay
• 21:05   Re: what server stats to track / monitor ? Rauan Maemirov

13 June 2009

• 20:23   Re: what server stats to track / monitor ? Joshua Tolley
• 22:37   Re: Censorship Dan Langille

15 June 2009

• 09:30   Postgres connection status as BIND Nimesh Satam
• 14:17   Re: Postgres connection status as BIND Tom Lane
• 15:08   Re: Postgres connection status as BIND Alan Hodgson

16 June 2009

• 13:45   Yet another slow nested loop Alexander Staubo
• 13:47   performance with query Alberto Dalmaso
• 13:56   Re: Yet another slow nested loop Dave Dutcher
• 13:58   Re: Yet another slow nested loop Alexander Staubo
• 14:13   Re: performance with query Joshua Tolley
• 14:21   Re: performance with query Kevin Grittner
• 14:37   Re: Yet another slow nested loop Tom Lane
• 14:48   Re: performance with query Alberto Dalmaso
• 15:09   Re: performance with query Matthew Wakeling
• 15:16   Re: performance with query Kevin Grittner
• 15:20   Re: performance with query Alberto Dalmaso
• 15:21   Re: Yet another slow nested loop Alexander Staubo
• 15:31   Re: performance with query Tom Lane
• 15:32   Re: performance with query Kevin Grittner
• 15:34   Re: performance with query Alberto Dalmaso
• 15:48   Re: performance with query Kevin Grittner
• 15:56   Re: performance with query Alberto Dalmaso
• 16:08   Re: performance with query Kevin Grittner
• 16:16   Re: performance with query Tom Lane
• 16:17   Re: performance with query Alberto Dalmaso
• 16:40   Re: performance with query Alberto Dalmaso
• 18:40   Speeding up a query. Hartman, Matthew
• 19:44   Re: Speeding up a query. Anthony Presley
• 21:08   Performance discrepancy Mark Steben
• 21:28   High cost of ... where ... not in (select ...) Aaron Turner
• 21:37   Re: High cost of ... where ... not in (select ...) Alvaro Herrera
• 23:47   Re: High cost of ... where ... not in (select ...) Aaron Turner

17 June 2009

• 00:30   Re: High cost of ... where ... not in (select ...) Robert Haas
• 01:23   Re: High cost of ... where ... not in (select ...) Aaron Turner
• 01:36   Re: High cost of ... where ... not in (select ...) Robert Haas
• 01:47   Re: High cost of ... where ... not in (select ...) Aaron Turner
• 01:47   Re: High cost of ... where ... not in (select ...) Aaron Turner
• 03:40   Index Scan taking long time Bryce Ewing
• 04:06   Re: High cost of ... where ... not in (select ...) Tom Lane
• 04:59   Re: Yet another slow nested loop Robert Haas
• 05:12   Re: Index Scan taking long time Scott Marlowe
• 05:46   8.4 COPY performance regression on Solaris Alan Li
• 07:10   Re: performance with query Alberto Dalmaso
• 07:17   Re: performance with query (OT) Albe Laurenz
• 07:33   Re: Speeding up a query. Albe Laurenz
• 07:42   Re: 8.4 COPY performance regression on Solaris Stefan Kaltenbrunner
• 08:40   Re: Speeding up a query. Grzegorz Jaśkiewicz
• 09:36   Re: Speeding up a query. Alberto Dalmaso
• 12:46   Re: GiST index performance Heikki Linnakangas
• 13:08   Re: Speeding up a query. Merlin Moncure
• 14:23   Re: Index Scan taking long time Tom Lane
• 14:48   Re: performance with query Kevin Grittner
• 14:55   Re: Speeding up a query. Kevin Grittner
• 15:05   Re: Speeding up a query. Hartman, Matthew
• 15:06   Re: Speeding up a query. Hartman, Matthew
• 15:07   Re: Speeding up a query. Tom Lane
• 15:13   Re: performance with query Alberto Dalmaso
• 15:18   Re: Speeding up a query. Hartman, Matthew
• 16:42   Re: performance with query Kevin Grittner
• 17:13   Performance issue - 2 linux machines, identical configs, different performance Mark Steben
• 17:32   Re: Performance issue - 2 linux machines, identical configs, different performance Robert Haas
• 17:39   Re: Performance issue - 2 linux machines, identical configs, different performance Dave Dutcher
• 18:05   Re: Performance issue - 2 linux machines, identical configs, different performance Mark Steben
• 18:36   very slow selects on a small table Brian Cox
• 21:44   Re: Index Scan taking long time Bryce Ewing
• 22:06   enum for performance? Whit Armstrong
• 22:12   Re: enum for performance? Tom Lane
• 22:29   Re: very slow selects on a small table Tom Lane
• 22:44   Re: Index Scan taking long time Tom Lane
• 22:49   Re: very slow selects on a small table Brian Cox
• 23:17   Re: very slow selects on a small table Tom Lane
• 23:25   Re: very slow selects on a small table Brian Cox
• 23:35   Re: very slow selects on a small table Tom Lane
• 23:42   Re: very slow selects on a small table Brian Cox

18 June 2009

• 00:07   Re: very slow selects on a small table Tom Lane
• 00:12   Re: very slow selects on a small table Brian Cox
• 00:17   Re: very slow selects on a small table Tom Lane
• 08:04   Re: performance with query Alberto Dalmaso
• 15:19   Re: enum for performance? Merlin Moncure
• 17:06   Re: very slow selects on a small table Brian Cox
• 17:12   Re: very slow selects on a small table Grzegorz Jaśkiewicz
• 17:17   Re: very slow selects on a small table Brian Cox
• 17:21   Re: very slow selects on a small table Grzegorz Jaśkiewicz
• 17:48   Re: very slow selects on a small table Tom Lane
• 18:27   Strange performance response for high load times Peter Alban
• 18:30   Re: Strange performance response for high load times Kenneth Marshall
• 19:27   Re: performance with query Kevin Grittner
• 19:39   Re: performance with query Tom Lane
• 19:42   Re: Strange performance response for high load times Peter Alban
• 19:54   Re: performance with query Kevin Grittner
• 20:01   Re: Strange performance response for high load times Kenneth Marshall
• 20:50   Re: Strange performance response for high load times Peter Alban
• 21:01   Re: Strange performance response for high load times Kevin Grittner
• 22:11   Re: Index Scan taking long time Bryce Ewing
• 23:34   select max() much slower than select min() Brian Cox

19 June 2009

• 00:15   Re: select max() much slower than select min() Kevin Grittner
• 00:40   Re: select max() much slower than select min() Brian Cox
• 01:11   Re: select max() much slower than select min() Kevin Grittner
• 13:33   Re: 8.4 COPY performance regression on Solaris Kenneth Marshall
• 14:14   Re: select max() much slower than select min() Dave Dutcher
• 14:26   Re: select max() much slower than select min() Tom Lane
• 14:38   Re: 8.4 COPY performance regression on Solaris Tom Lane
• 15:20   Re: select max() much slower than select min() Greg Stark
• 16:00   processor running queue - general rule of thumb? Alan McKay
• 19:11   Re: processor running queue - general rule of thumb? justin
• 19:34   Re: processor running queue - general rule of thumb? Scott Marlowe
• 19:48   Re: processor running queue - general rule of thumb? Alan McKay
• 20:05   Re: select max() much slower than select min() Brian Cox
• 20:42   Re: select max() much slower than select min() David Rees
• 21:05   Re: select max() much slower than select min() Brian Cox
• 23:39   Re: select max() much slower than select min() David Rees

21 June 2009

• 10:54   same query in high number of times Peter Alban
• 14:00   Re: same query in high number of times Justin Graf
• 17:42   Re: same query in high number of times Robert Haas
• 18:28   Re: same query in high number of times Peter Alban
• 20:00   Re: same query in high number of times Justin Graf
• 20:36   Re: same query in high number of times Grzegorz Jaśkiewicz
• 20:50   Re: same query in high number of times Justin Graf
• 20:59   Re: same query in high number of times Peter Alban
• 22:06   Re: same query in high number of times Scott Marlowe
• 22:08   Re: same query in high number of times Justin Graf

22 June 2009

• 03:23   Re: same query in high number of times Robert Haas
• 21:39   Re: same query in high number of times Peter Alban
• 23:06   Re: same query in high number of times Scott Carey

23 June 2009

• 08:52   Re: same query in high number of times Laurent Laborde
• 08:55   Re: same query in high number of times Laurent Laborde
• 11:34   How would you store read/unread topic status? Mathieu Nebra
• 12:24   Re: How would you store read/unread topic status? Andres Freund
• 12:37   Re: How would you store read/unread topic status? Alexander Staubo
• 12:43   Re: How would you store read/unread topic status? Andres Freund
• 13:58   Re: How would you store read/unread topic status? justin
• 14:11   Re: How would you store read/unread topic status? Nikolas Everett
• 14:22   Re: How would you store read/unread topic status? Matthew Wakeling
• 14:53   Re: How would you store read/unread topic status? Mathieu Nebra
• 15:00   Re: How would you store read/unread topic status? Mathieu Nebra
• 15:04   Re: How would you store read/unread topic status? Robert Haas
• 15:12   Re: How would you store read/unread topic status? Guillaume Cottenceau
• 15:14   Re: How would you store read/unread topic status? Andres Freund
• 15:30   Re: How would you store read/unread topic status? Robert Haas
• 15:34   Re: How would you store read/unread topic status? Grzegorz Jaśkiewicz
• 15:50   Re: How would you store read/unread topic status? Mathieu Nebra
• 16:06   Re: How would you store read/unread topic status? Robert Haas
• 16:31   Re: How would you store read/unread topic status? Mike
• 16:36   Re: How would you store read/unread topic status? Mike
• 17:05   Re: How would you store read/unread topic status? Scott Carey
• 17:17   Re: How would you store read/unread topic status? Scott Carey
• 19:44   Re: How would you store read/unread topic status? Greg Stark
• 20:03   Implications of having large number of users Mike Ivanov
• 20:04   Re: How would you store read/unread topic status? Mathieu Nebra
• 20:14   Re: How would you store read/unread topic status? Alexander Staubo
• 20:41   Re: processor running queue - general rule of thumb? Alan McKay
• 21:29   Re: How would you store read/unread topic status? Craig James
• 23:21   SOLVED: processor running queue - general rule of thumb? Alan McKay
• 23:48   Re: How would you store read/unread topic status? Greg Stark

24 June 2009

• 07:16   Re: How would you store read/unread topic status? Chris St Denis
• 07:20   tsvector_update_trigger performance? Chris St Denis
• 07:27   Re: tsvector_update_trigger performance? Oleg Bartunov
• 07:42   Re: How would you store read/unread topic status? Mathieu Nebra
• 08:08   Re: How would you store read/unread topic status? Mathieu Nebra
• 08:33   Re: Implications of having large number of users Albe Laurenz
• 11:30   Re: Implications of having large number of users Robert Haas
• 12:49   Nested Loop "Killer" on 8.1 Dave North
• 13:03   Re: Implications of having large number of users Albe Laurenz
• 13:53   Re: Implications of having large number of users Tom Lane
• 14:30   Re: Implications of having large number of users Robert Haas
• 16:29   Re: tsvector_update_trigger performance? Alvaro Herrera
• 17:32   cluster index on a table Ibrahim Harrani
• 17:40   Re: cluster index on a table Kenneth Marshall
• 17:42   Re: cluster index on a table Scott Marlowe
• 20:04   Re: tsvector_update_trigger performance? Dimitri Fontaine

25 June 2009

• 04:03   Re: tsvector_update_trigger performance? Chris St Denis
• 05:45   Re: tsvector_update_trigger performance? Craig Ringer
• 07:42   Re: tsvector_update_trigger performance? Dimitri Fontaine
• 18:19   Re: Implications of having large number of users Mike Ivanov
• 20:16   Re: Nested Loop "Killer" on 8.1 Josh Berkus
• 20:37   Re: Nested Loop "Killer" on 8.1 Greg Stark
• 20:56   Re: Nested Loop "Killer" on 8.1 Mark Mielke
• 21:05   Re: Nested Loop "Killer" on 8.1 Tom Lane
• 21:30   Re: Nested Loop "Killer" on 8.1 Greg Stark

26 June 2009

• 02:38   slow DELETE on 12 M row table Janet Jacobsen
• 03:18   Re: slow DELETE on 12 M row table Greg Stark
• 05:47   Re: slow DELETE on 12 M row table Richard Huxton
• 07:33   Re: slow DELETE on 12 M row table Janet Jacobsen
• 11:12   Re: slow DELETE on 12 M row table Marcin Stępnicki
• 14:33   Re: GiST index performance Greg Smith
• 15:00   Re: GiST index performance Robert Haas
• 17:25   Insert performance and multi-column index order bob_lunney@yahoo.com
• 17:40   Re: Nested Loop "Killer" on 8.1 Dave North
• 19:30   Terrible Write Performance of a Stored Procedure Brian Troutwine
• 19:40   Re: Terrible Write Performance of a Stored Procedure Alan Hodgson
• 19:48   Re: Terrible Write Performance of a Stored Procedure Merlin Moncure
• 20:35   Re: Terrible Write Performance of a Stored Procedure Brian Troutwine
• 20:39   Re: Terrible Write Performance of a Stored Procedure Brian Troutwine
• 21:03   Re: Terrible Write Performance of a Stored Procedure Scott Mead
• 22:22   Re: Nested Loop "Killer" on 8.1 Tom Lane
• 22:37   Re: Terrible Write Performance of a Stored Procedure Greg Smith
• 23:19   Re: Insert performance and multi-column index order Tom Lane

27 June 2009

• 01:17   Re: slow DELETE on 12 M row table Janet Jacobsen
• 01:36   Re: slow DELETE on 12 M row table Robert Haas
• 03:27   Re: what server stats to track / monitor ? Greg Smith
• 05:08   Re: Insert performance and multi-column index order Greg Smith

28 June 2009

• 01:25   Re: slow DELETE on 12 M row table Scott Carey
• 02:09   Re: slow DELETE on 12 M row table Robert Haas
• 13:52   Re: what server stats to track / monitor ? Alan McKay

29 June 2009

• 12:54   Re: Terrible Write Performance of a Stored Procedure Scott Mead
• 13:33   random slow query Sean Ma
• 13:36   Re: random slow query Andres Freund
• 14:31   Utilizing multiple cores in a function call. Hartman, Matthew
• 14:53   Re: Utilizing multiple cores in a function call. Jean-David Beyer
• 14:53   Re: random slow query Kevin Grittner
• 15:08   Re: Utilizing multiple cores in a function call. Hartman, Matthew
• 18:20   Re: Utilizing multiple cores in a function call. Joe Conway
• 18:43   Re: Utilizing multiple cores in a function call. Greg Smith
• 21:21   Re: Utilizing multiple cores in a function call. Merlin Moncure
• 23:26   Re: random slow query Mike Ivanov

30 June 2009

• 05:54   Re: Utilizing multiple cores in a function call. Craig Ringer
• 09:12   Re: Terrible Write Performance of a Stored Procedure valgog
• 12:31   Re: Insert performance and multi-column index order Bob Lunney
• 12:35   Re: Utilizing multiple cores in a function call. Hartman, Matthew
• 13:19   Re: Utilizing multiple cores in a function call. Merlin Moncure
• 13:35   Re: Utilizing multiple cores in a function call. Hartman, Matthew
• 14:21   Re: random slow query Sean Ma
• 17:24   Re: random slow query Mike Ivanov
• 17:46   Re: random slow query Scott Marlowe
• 17:49   Re: random slow query Sean Ma
• 17:59   Re: random slow query Scott Marlowe
• 18:00   Re: random slow query Mike Ivanov
• 18:02   Re: random slow query Mike Ivanov
• 18:06   Re: random slow query Scott Marlowe
• 18:31   Re: random slow query Mike Ivanov
• 18:33   Re: random slow query Scott Marlowe
• 18:34   Re: random slow query Scott Marlowe
• 18:47   Re: random slow query Alan Hodgson
• 19:02   Re: random slow query Mike Ivanov
• 19:06   Re: random slow query Jean-David Beyer
• 19:10   Re: random slow query Mike Ivanov
• 20:08   Re: random slow query Scott Carey
• 20:46   Re: random slow query Scott Carey
• 21:20   Re: random slow query Scott Carey
• 21:40   Re: random slow query Mike Ivanov