Mailing lists [pgsql-performance]

1 July 2004

• 01:35   planner and worst case scenario Joseph Shraibman
• 13:51   network address query Litao Wu
• 16:20   Query gets slow when where clause increases James Antill
• 18:45   Re: Query gets slow when where clause increases Dennis Bjorklund

2 July 2004

• 04:47   Mysterious performance of query because of plsql function in where condition Peter Alberer
• 08:52   Re: Mysterious performance of query because of plsql function in where condition Jeff
• 10:00   Re: Mysterious performance of query because of plsql function in where condition Bruno Wolff III
• 10:06   Re: BUG #1186: Broken Index? Bruno Wolff III

5 July 2004

• 07:11   Seq scan vs. Index scan with different query conditions [email protected]
• 08:41   Re: Seq scan vs. Index scan with different query conditions Richard Huxton
• 08:44   Re: Seq scan vs. Index scan with different query Andrew McMillan
• 10:42   Re: Seq scan vs. Index scan with different query conditions [email protected]
• 16:24   Re: Seq scan vs. Index scan with different query Andrew McMillan

6 July 2004

• 12:00   to fsync or not to fsync Rodrigo Filgueira
• 12:45   Re: to fsync or not to fsync Frank Hsueh
• 13:50   Re: to fsync or not to fsync (ext3?) Rodrigo Filgueira
• 14:54   Keyword searching question borajetta
• 14:57   Re: Keyword searching question borajetta

7 July 2004

• 12:13   Implementatiion of Inheritance in Postgres Ioannis Theoharis
• 13:17   Terrible performance after deleting/recreating indexes Bill Chandler
• 14:24   inserting into brand new database faster than old database Missner, T. R.
• 16:04   Forcing HashAggregation prior to index scan? Eugene
• 16:15   finding a max value Edoardo Ceccarelli
• 16:19   Odd sorting behaviour Steinar H. Gunderson
• 16:20   Re: Mysterious performance of query because of plsql function in CoL
• 16:25   Re: inserting into brand new database faster than old database Matthew T. O'Connor
• 16:28   Re: inserting into brand new database faster than old database Missner, T. R.
• 17:34   Re: finding a max value Rosser Schwarz
• 18:27   query plan wierdness? Joel McGraw
• 19:12   Re: query plan wierdness? Joel McGraw
• 19:50   Re: query plan wierdness? Stephan Szabo

8 July 2004

• 06:02   Re: inserting into brand new database faster than old database Shridhar Daithankar
• 06:07   Re: Terrible performance after deleting/recreating indexes Shridhar Daithankar
• 07:19   Odd sorting behaviour Steinar H. Gunderson
• 13:13   Re: finding a max value James Antill
• 13:16   Re: query plan wierdness? Guido Barosio
• 13:51   Re: query plan wierdness? Rod Taylor
• 15:03   vacuum_mem Litao Wu
• 15:26   Re: vacuum_mem Rod Taylor
• 17:49   Re: Terrible performance after deleting/recreating indexes Bill Chandler
• 21:13   Re: Terrible performance after deleting/recreating indexes Mark Kirkwood
• 21:31   Working on huge RAM based datasets Andy Ballingall
• 22:35   Re: Working on huge RAM based datasets Christopher Kings-Lynne

9 July 2004

• 11:16   Re: Working on huge RAM based datasets Merlin Moncure
• 12:18   Re: Terrible performance after deleting/recreating indexes Bill Chandler
• 15:15   Re: query plan wierdness? Joel McGraw
• 16:18   Re: query plan wierdness? Rod Taylor
• 17:24   Cursors performance (was: Re: Terrible performance after deleting/recreating indexes) Bill Chandler
• 17:38   Re: [JDBC] Cursors performance (was: Re: Terrible Dave Cramer
• 17:44   Re: [JDBC] Cursors performance (was: Re: Terrible performance Kris Jurka
• 18:17   Re: Working on huge RAM based datasets Andy Ballingall
• 18:17   Re: Working on huge RAM based datasets Andy Ballingall
• 19:22   Re: [JDBC] Cursors performance Oliver Jowett
• 23:52   Re: inserting into brand new database faster than old database Tom Lane

10 July 2004

• 00:04   Re: Cursors performance Mark Kirkwood
• 00:10   Re: Forcing HashAggregation prior to index scan? Tom Lane
• 07:00   Re: achat borne wifi Laurent Martelli
• 10:59   Re: Working on huge RAM based datasets Christopher Browne

11 July 2004

• 11:14   Re: Working on huge RAM based datasets Jan Wieck
• 14:59   Re: Working on huge RAM based datasets Christopher Browne

12 July 2004

• 11:05   Re: Working on huge RAM based datasets Merlin Moncure
• 11:22   Re: Working on huge RAM based datasets Merlin Moncure
• 11:38   Re: Working on huge RAM based datasets Rod Taylor
• 13:39   Re: Working on huge RAM based datasets Josh Berkus
• 15:02   Re: Working on huge RAM based datasets Jan Wieck
• 15:34   Re: Fw: invitation au "Village du Logiciel Libre" de la Laurent Martelli
• 20:54   Re: query plan wierdness? Joel McGraw
• 23:11   Re: query plan wierdness? Rod Taylor

13 July 2004

• 02:54   How to create an index for type timestamp column using rtree? Chris Cheston
• 03:25   Re: How to create an index for type timestamp column using rtree? Tom Lane
• 03:31   Re: How to create an index for type timestamp column using Christopher Kings-Lynne
• 04:56   Re: How to create an index for type timestamp column using rtree? Chris Cheston
• 13:51   Insert are going slower ... Hervé Piedvache
• 14:10   Re: Insert are going slower ... Josh Berkus
• 16:29   Re: Working on huge RAM based datasets Andy Ballingall
• 16:29   Re: Inverted-list databases (was: Working on huge RAM based datasets) Mischa Sandberg
• 16:29   Swapping in 7.4.3 Jim Ewert
• 17:28   Re: Swapping in 7.4.3 Matthew T. O'Connor
• 20:42   Re: Insert are going slower ... Hervé Piedvache

14 July 2004

• 07:04   Re: Insert are going slower ... gnari
• 07:13   Re: Insert are going slower ... Shridhar Daithankar
• 11:08   Re: Insert are going slower ... Hervé Piedvache
• 11:32   Re: Insert are going slower ... Shridhar Daithankar
• 13:41   Re: Insert are going slower ... Josh Berkus
• 18:19   Re: Insert are going slower ... Hervé Piedvache
• 18:32   Re: Insert are going slower ... Hervé Piedvache
• 18:41   vacuum full 100 mins plus? Patrick Hatcher
• 19:48   Re: vacuum full 100 mins plus? Patrick Hatcher
• 20:11   Re: Odd sorting behaviour Steinar H. Gunderson
• 21:13   Re: vacuum full 100 mins plus? Josh Berkus
• 22:40   Re: Odd sorting behaviour Josh Berkus

15 July 2004

• 00:02   Re: vacuum full 100 mins plus? Christopher Browne
• 01:37   Re: vacuum full 100 mins plus? Tom Lane
• 01:53   Re: Odd sorting behaviour Tom Lane
• 03:22   Re: Insert are going slower ... Shridhar Daithankar
• 09:08   Re: Odd sorting behaviour Steinar H. Gunderson
• 10:49   Re: Swapping in 7.4.3 Jim Ewert
• 12:30   Re: vacuum full 100 mins plus? Mike Rylander
• 13:19   Re: Swapping in 7.4.3 Scott Marlowe
• 15:07   hardware raid suggestions Brian Hirt
• 15:09   Re: Insert are going slower ... Josh Berkus
• 15:11   Re: Odd sorting behaviour Josh Berkus
• 19:16   Re: Odd sorting behaviour Steinar H. Gunderson
• 23:55   Re: hardware raid suggestions Josh Berkus

16 July 2004

• 00:25   Re: hardware raid suggestions Mark Aufflick
• 04:36   Re: Swapping in 7.4.3 Matt Clark
• 08:17   Re: Insert are going slower ... Hervé Piedvache
• 15:37   Wierd issues Andrew Matthews
• 15:37   extrem bad performance Stefan
• 18:36   same plan, different time Litao Wu
• 23:31   Re: extrem bad performance Rod Taylor

17 July 2004

• 00:20   Re: hardware raid suggestions Fred Moyer
• 00:31   Scaling with lazy index updates Fred Moyer
• 01:53   Re: same plan, different time Tom Lane
• 21:02   Re: Scaling with lazy index updates Josh Berkus

18 July 2004

• 06:42   Re: High load average with PostgreSQL 7.4.2 on debian/ibm eserver. Gaetano Mendola
• 14:24   Re: Insert are going slower ... Josh Berkus

20 July 2004

• 04:50   NAS, SAN or any alternate solution ? [email protected]
• 05:20   Re: NAS, SAN or any alternate solution ? Scott Marlowe
• 06:29   Réf. : Re: NAS, SAN or any alternatesolution ? [email protected]
• 07:02   Re: Réf. : Re: [PERFORM] NAS, Mark Kirkwood
• 07:15   Réf. : Re: Réf. : Re: NAS, SANor any alternate solution ? [email protected]
• 07:45   Re: Working on huge RAM based datasets abhousehunt
• 08:51   Re: Odd sorting behaviour Steinar H. Gunderson
• 09:26   Re: NAS, SAN or any alternate solution ? Grega Bremec
• 10:04   Re: NAS, SAN or any alternate solution ? Grega Bremec
• 12:27   Re: Réf. : Re: NAS, SAN or any Scott Marlowe
• 13:45   Re: NAS, SAN or any alternate solution ? Joe Conway
• 14:03   Re: Odd sorting behaviour Josh Berkus
• 14:07   Re: Odd sorting behaviour Josh Berkus
• 14:21   Re: Odd sorting behaviour Steinar H. Gunderson
• 14:30   Re: NAS, SAN or any alternate solution ? Rod Taylor
• 16:19   Unbearably slow cascading deletes [email protected]
• 16:45   Re: Unbearably slow cascading deletes Stephan Szabo
• 16:55   Re: Unbearably slow cascading deletes Stephan Szabo
• 16:59   Re: Unbearably slow cascading deletes [email protected]
• 17:07   Re: Unbearably slow cascading deletes [email protected]
• 22:36   Re: Unbearably slow cascading deletes Christopher Kings-Lynne
• 23:22   Re: Odd sorting behaviour Rod Taylor

21 July 2004

• 07:04   Re: Odd sorting behaviour Steinar H. Gunderson
• 11:58   Re: Odd sorting behaviour Rod Taylor
• 13:46   Re: extrem bad performance Stefan
• 17:46   Beowulf Cluster & Postgresql? joe
• 18:07   Re: Beowulf Cluster & Postgresql? Scott Marlowe
• 23:48   Re: Beowulf Cluster & Postgresql? Mark Kirkwood

23 July 2004

• 02:53   Performance over a LAN William Carney
• 03:00   Re: Performance over a LAN Christopher Kings-Lynne
• 03:20   Re: Performance over a LAN Mark Aufflick
• 03:28   Re: Performance over a LAN Scott Marlowe
• 05:00   Re: Performance over a LAN William Carney
• 08:43   Re: Performance over a LAN Rod Taylor
• 09:05   Re: Performance over a LAN Jeff
• 12:34   Re: Performance over a LAN Michael Adler
• 13:26   Re: Performance over a LAN Gary Cowell
• 14:10   Re: Performance over a LAN Greg Stark
• 14:42   Re: [HACKERS] Wrong index choosen? Gaetano Mendola
• 15:12   Re: [HACKERS] Wrong index choosen? Matthew T. O'Connor
• 18:51   Re: [HACKERS] Wrong index choosen? Jaime Casanova
• 19:01   Re: [HACKERS] Wrong index choosen? Scott Marlowe
• 21:08   Re: [HACKERS] Wrong index choosen? Gaetano Mendola
• 22:49   Re: [HACKERS] Wrong index choosen? Matthew T. O'Connor

25 July 2004

• 20:09   Index type Ilia Kantor
• 20:09   Re: Working on huge RAM based datasets Andy Ballingall
• 20:09   variable length - user defined types/storage place [email protected]

26 July 2004

• 01:57   arrays and indexes Ross J. Reedstrom
• 03:27   Re: arrays and indexes Greg Stark
• 11:16   Re: Insert are going slower ... Gaetano Mendola
• 11:16   Re: hardware raid suggestions Gaetano Mendola
• 11:47   Re: Insert are going slower ... Gaetano Mendola
• 11:52   Timestamp-based indexing Harmon S. Nine
• 11:56   Re: arrays and indexes Merlin Moncure
• 12:05   Re: Timestamp-based indexing Kevin Barnard
• 12:10   Re: Timestamp-based indexing Matthew T. O'Connor
• 12:43   Re: Timestamp-based indexing Harmon S. Nine
• 12:46   Re: Timestamp-based indexing Harmon S. Nine
• 12:59   Re: Timestamp-based indexing Tom Lane
• 13:02   Re: Timestamp-based indexing Stephan Szabo
• 13:24   Re: Insert are going slower ... Scott Marlowe
• 15:37   Re: Timestamp-based indexing Harmon S. Nine
• 15:57   Re: arrays and indexes Ross J. Reedstrom
• 17:35   Re: arrays and indexes Pierre-Frédéric Caillaud
• 17:40   Re: arrays and indexes Greg Stark
• 18:21   Re: arrays and indexes Tom Lane
• 18:27   Re: Timestamp-based indexing Litao Wu
• 18:40   Re: Timestamp-based indexing Tom Lane
• 22:52   Re: Timestamp-based indexing Christopher Kings-Lynne

27 July 2004

• 01:33   Re: arrays and indexes Greg Stark
• 04:35   Little understanding for tuning ... Hervé Piedvache
• 10:07   best way to fetch next/prev record based on index Merlin Moncure
• 10:15   Automagic tuning Markus Schaber

28 July 2004

• 00:22   Re: best way to fetch next/prev record based on index Tom Lane
• 00:26   Re: best way to fetch next/prev record based on index Merlin Moncure
• 00:30   best way to fetch next/prev record based on index Merlin Moncure
• 00:30   Re: best way to fetch next/prev record based on index Greg Stark
• 00:30   Re: best way to fetch next/prev record based on index Tom Lane
• 00:31   Re: best way to fetch next/prev record based on index Markus Schaber
• 00:34   Re: best way to fetch next/prev record based on index Rod Taylor
• 00:35   Re: best way to fetch next/prev record based on index Merlin Moncure
• 00:35   Re: Automagic tuning Christopher Kings-Lynne
• 00:35   Re: best way to fetch next/prev record based on index Tom Lane
• 00:36   Correction of best way to fetch next/prev record based on index Markus Schaber
• 00:36   Re: best way to fetch next/prev record based on index [email protected]
• 00:43   Re: best way to fetch next/prev record based on index Markus Schaber
• 00:46   Re: best way to fetch next/prev record based on index Merlin Moncure
• 00:47   Re: best way to fetch next/prev record based on index Tom Lane
• 00:48   Re: best way to fetch next/prev record based on index Merlin Moncure
• 00:50   Re: best way to fetch next/prev record based on index Greg Stark
• 00:51   Re: best way to fetch next/prev record based on index Merlin Moncure
• 00:52   Re: best way to fetch next/prev record based on index Merlin Moncure
• 01:01   Re: best way to fetch next/prev record based on index Stephan Szabo
• 02:53   Re: best way to fetch next/prev record based on index Greg Stark
• 04:15   Re: best way to fetch next/prev record based on index Greg Stark
• 09:48   Re: best way to fetch next/prev record based on index Merlin Moncure
• 11:07   Re: best way to fetch next/prev record based on index Tom Lane
• 12:38   Re: best way to fetch next/prev record based on index Merlin Moncure
• 13:01   Re: best way to fetch next/prev record based on index Greg Stark
• 13:54   Join performance Pierre-Frédéric Caillaud
• 13:56   Re: best way to fetch next/prev record based on index Tom Lane
• 19:54   Re: best way to fetch next/prev record based on index Greg Stark
• 20:12   Re: best way to fetch next/prev record based on index Tom Lane

29 July 2004

• 12:32   Optimizer refuses to hash join Stan Bielski
• 12:48   my boss want to migrate to ORACLE Stephane Tessier
• 12:55   Extremely slow query... [email protected]
• 13:14   Re: Optimizer refuses to hash join Stephan Szabo
• 13:49   Re: best way to fetch next/prev record based on index Merlin Moncure
• 14:07   Re: Optimizer refuses to hash join Tom Lane
• 14:58   Re: best way to fetch next/prev record based on index Greg Stark
• 15:23   Re: best way to fetch next/prev record based on index Merlin Moncure
• 15:41   Re: best way to fetch next/prev record based on index Tom Lane
• 15:49   Re: best way to fetch next/prev record based on index Greg Stark
• 17:12   Re: best way to fetch next/prev record based on index Merlin Moncure
• 18:05   Index works with foo.val=bar.val but not foo.val<=bar.val [email protected]
• 22:22   Re: my boss want to migrate to ORACLE Russell Smith
• 23:34   Re: my boss want to migrate to ORACLE [email protected]

30 July 2004

• 00:00   Re: my boss want to migrate to ORACLE [email protected]
• 09:33   Re: my boss want to migrate to ORACLE Jeff
• 10:56   Re: my boss want to migrate to ORACLE Stephane Tessier
• 11:14   Re: my boss want to migrate to ORACLE Merlin Moncure
• 12:13   Re: my boss want to migrate to ORACLE Scott Marlowe
• 13:49   Re: Optimizer refuses to hash join Tom Lane
• 14:56   Re: my boss want to migrate to ORACLE Matthew T. O'Connor
• 15:12   Re: my boss want to migrate to ORACLE Dan Langille
• 15:29   Re: my boss want to migrate to ORACLE Brian Hirt
• 23:17   Re: my boss want to migrate to ORACLE Christopher Browne

31 July 2004

• 01:17   Re: my boss want to migrate to ORACLE Scott Marlowe