Postgres Performance Date Index

• Thread Index

• Re: 15,000 tables
  • From: Guido Neitzer
• Re: Queries taking ages in PG 8.1, have been much faster in PG<=8.0
  • From: Markus Wollny
• Re: Queries taking ages in PG 8.1, have been much faster in PG<=8.0
  • From: Tom Lane
• Re: 15,000 tables
  • From: Michael Riess
• Re: pg_dump slow
  • From: Merlin Moncure
• Re: 15,000 tables
  • From: Jaime Casanova
• Re: 15,000 tables
  • From: Tom Lane
• Re: slow insert into very large table
  • From: Tom Lane
• Queries taking ages in PG 8.1, have been much faster in PG<=8.0
  • From: Markus Wollny
• Re: 15,000 tables
  • From: Jaime Casanova
• Re: About the relation between fragmentation of file and
  • From: David Lang
• Re: 15,000 tables
  • From: Michael Riess
• Re: 15,000 tables
  • From: Michael Riess
• filesystem performance with lots of files
  • From: David Lang
• Re: 15,000 tables
  • From: David Lang
• Re: slow insert into very large table
  • From: Andreas Pflug
• 15,000 tables
  • From: Michael Riess
• slow insert into very large table
  • From: Wolfgang Gehner
• Re: About the relation between fragmentation of file and VACUUM
  • From: Bill McGonigle
• Re: About the relation between fragmentation of file and
  • From: Michael Stone
• pg_dump slow
  • From: Franklin Haut
• Re: About the relation between fragmentation of file and
  • From: Richard Huxton
• About the relation between fragmentation of file and VACUUM
  • From: Tatsumi Abe
• Re: Query is 800 times slower when running in function!
  • From: Tom Lane
• Re: index auto changes after copying data ?
  • From: Chris Browne
• Re: index auto changes after copying data ?
  • From: Richard Huxton
• index auto changes after copying data ?
  • From: energumen@xxxxxxxxxxx
• Re: Hardware/OS recommendations for large databases (
  • From: David Lang
• Re: Hardware/OS recommendations for large databases (
  • From: David Lang
• Re: Hardware/OS recommendations for large databases (
  • From: David Boreham
• Re: Hardware/OS recommendations for large databases (
  • From: Brendan Duddridge
• Re: Please help with this explain analyse...
  • From: David Gagnon
• Re: Please help with this explain analyse...
  • From: Tom Lane
• Re: Please help with this explain analyse...
  • From: Bricklen Anderson
• Re: Hardware/OS recommendations for large databases (
  • From: Brendan Duddridge
• Please help with this explain analyse...
  • From: David Gagnon
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Hardware/OS recommendations for large databases (
  • From: Merlin Moncure
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Newbie question: ultra fast count(*)
  • From: Merlin Moncure
• Re: Hardware/OS recommendations for large databases (
  • From: Stephan Szabo
• Re: Open request for benchmarking input
  • From: David Lang
• Re: Hardware/OS recommendations for large databases
  • From: Ron
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases
  • From: Ron
• Re: Hardware/OS recommendations for large databases (
  • From: Stephan Szabo
• Re: Open request for benchmarking input
  • From: Andreas Pflug
• Re: Open request for benchmarking input
  • From: Steinar H. Gunderson
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: David Lang
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: David Lang
• Open request for benchmarking input
  • From: David Lang
• Re: Open request for benchmarking input
  • From: David Lang
• Re: Open request for benchmarking input
  • From: David Lang
• Re: Open request for benchmarking input
  • From: Andreas Pflug
• Re: Open request for benchmarking input
  • From: Ron
• Re: Open request for benchmarking input
  • From: Luke Lonergan
• Re: Open request for benchmarking input
  • From: Qingqing Zhou
• Open request for benchmarking input
  • From: Jeff Frost
• Re: Newbie question: ultra fast count(*)
  • From: Jaime Casanova
• Newbie question: ultra fast count(*)
  • From: Rodrigo Madera
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Pailloncy Jean-Gerard
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Alvaro Herrera
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Steinar H. Gunderson
• Re: xlog flush request error
  • From: Tom Lane
• Re: xlog flush request error
  • From: Vipul . Gupta
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Kyle Cordes
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Tom Lane
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Pailloncy Jean-Gerard
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Very slow queries - please help
  • From: Bealach-na Bo
• Re: Very slow queries - please help
  • From: Bealach-na Bo
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Greg Stark
• Re: Hardware/OS recommendations for large databases (
  • From: Tom Lane
• Re: Hardware/OS recommendations for large databases (
  • From: Greg Stark
• Re: xlog flush request error
  • From: Tom Lane
• Re: Very slow queries - please help.
  • From: Tom Lane
• Re: Very slow queries - please help.
  • From: Guillaume Smet
• Re: Very slow queries - please help.
  • From: Bealach-na Bo
• Re: High context switches occurring
  • From: Sven Geisler
• Re: Very slow queries - please help.
  • From: Claus Guttesen
• Very slow queries - please help.
  • From: Bealach-na Bo
• xlog flush request error
  • From: Vipul . Gupta
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Pailloncy Jean-Gerard
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Pailloncy Jean-Gerard
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: andrew
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Tom Lane
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• 8.1 count(*) distinct: IndexScan/SeqScan
  • From: Pailloncy Jean-Gerard
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: High context switches occurring
  • From: Anjan Dave
• Re: High context switches occurring
  • From: Anjan Dave
• Re: High context switches occurring
  • From: Simon Riggs
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Stored Procedure
  • From: Michael Fuhr
• Re: Stored Procedure
  • From: Michael Fuhr
• Re: Hardware/OS recommendations for large databases (
  • From: Bruce Momjian
• Re: Hardware/OS recommendations for large databases (
  • From: Greg Stark
• Re: Binary Refcursor possible?
  • From: Ralph Mason
• Re: Binary Refcursor possible?
  • From: Tom Lane
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Binary Refcursor possible?
  • From: Ralph Mason
• Re: Hardware/OS recommendations for large databases (
  • From: Bruce Momjian
• Re: High context switches occurring
  • From: Anjan Dave
• Re: Stored Procedure
  • From: Yves Vindevogel
• Re: Stored Procedure
  • From: Yves Vindevogel
• Re: High context switches occurring
  • From: Scott Marlowe
• Re: High context switches occurring
  • From: Scott Marlowe
• Re: High context switches occurring
  • From: Anjan Dave
• Re: High context switches occurring
  • From: Tom Lane
• Re: High context switches occurring
  • From: Anjan Dave
• Re: Stored Procedure
  • From: Michael Fuhr
• Re: Stored Procedure
  • From: Jim Buttafuoco
• Stored Procedure
  • From: Yves Vindevogel
• Re: High context switches occurring
  • From: Tom Lane
• Re: System queue
  • From: Jeff Trout
• Re: weird performances problem
  • From: Ron
• Re: High context switches occurring
  • From: Vivek Khera
• High context switches occurring
  • From: Anjan Dave
• Re: System queue
  • From: Frank Wiles
• Re: weird performances problem
  • From: Guillaume Smet
• Re: weird performances problem
  • From: Ron
• Re: weird performances problem
  • From: Guillaume Smet
• System queue
  • From: Marek Dabrowski
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: weird performances problem
  • From: Guillaume Smet
• Re: Strange query plan invloving a view
  • From: Rich Doughty
• Re: weird performances problem
  • From: Ron
• Re: weird performances problem
  • From: Guillaume Smet
• Re: weird performances problem
  • From: Guillaume Smet
• Re: weird performances problem
  • From: Qingqing Zhou
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Michael Stone
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: VERY slow after many updates
  • From: Scott Marlowe
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Michael Stone
• Re: Hardware/OS recommendations for large databases (
  • From: Bill McGonigle
• Re: Hardware/OS recommendations for large databases (
  • From: Alvaro Herrera
• Re: Hardware/OS recommendations for large databases (
  • From: Greg Stark
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Tom Lane
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Hyperthreading slows processes?
  • From: Dave Cramer
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Hyperthreading slows processes?
  • From: Craig A. James
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Steinar H. Gunderson
• Re: Hardware/OS recommendations for large databases (
  • From: Greg Stark
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Steinar H. Gunderson
• Re: Hardware/OS recommendations for large databases (
  • From: William Yu
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Perl DBD and an alarming problem
  • From: Craig A. James
• Re: Storage/Performance and splitting a table
  • From: Michael Stone
• Storage/Performance and splitting a table
  • From: Craig A. James
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: What is the max number of database I can create in
  • From: John McCawley
• Re: VERY slow after many updates
  • From: Alex Wang
• Re: VERY slow after many updates
  • From: Guido Neitzer
• Re: VERY slow after many updates
  • From: Csaba Nagy
• Re: VERY slow after many updates
  • From: Alex Wang
• Re: VERY slow after many updates
  • From: Csaba Nagy
• VERY slow after many updates
  • From: Alex Wang
• Re: What is the max number of database I can create in an instance of pgsql?
  • From: Jaime Casanova
• Re: What is the max number of database I can create in an instance of pgsql?
  • From: Michael Glaesemann
• What is the max number of database I can create in an instance of pgsql?
  • From: anon permutation
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: ERROR: no value found for parameter 1 with JDBC and Explain Analyze
  • From: Tom Lane
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Mark Kirkwood
• Re: Help speeding up delete
  • From: Leigh Dyer
• sort/limit across union all
  • From: Marc Morin
• ERROR: no value found for parameter 1 with JDBC and Explain Analyze
  • From: Virag Saksena
• Re: Hardware/OS recommendations for large databases
  • From: Ron
• Re: Hardware/OS recommendations for large databases (
  • From: Dave Cramer
• Re: weird performances problem
  • From: Andrew Sullivan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Greg Stark
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Alex Turner
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Bill McGonigle
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Vivek Khera
• Re: Hardware/OS recommendations for large databases (
  • From: Vivek Khera
• Re: Hardware/OS recommendations for large databases (
  • From: Dave Cramer
• Re: Hardware/OS recommendations for large databases
  • From: Ron
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: Hardware/OS recommendations for large databases (
  • From: Richard Huxton
• Re: Hardware/OS recommendations for large databases (
  • From: Dave Cramer
• Re: Hardware/OS recommendations for large databases (
  • From: Dave Cramer
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Perl DBD and an alarming problem
  • From: Michael Fuhr
• Re: Hardware/OS recommendations for large databases (
  • From: Greg Stark
• Re: Hardware/OS recommendations for large databases (
  • From: Greg Stark
• Re: Help speeding up delete
  • From: Christopher Kings-Lynne
• Re: Help speeding up delete
  • From: Ron Mayer
• Re: weird performances problem
  • From: Claus Guttesen
• Re: Hardware/OS recommendations for large databases (
  • From: Alan Stange
• Re: weird performances problem
  • From: Guillaume Smet
• Re: Perl DBD and an alarming problem
  • From: Michael Fuhr
• Re: weird performances problem
  • From: Andrew Sullivan
• Re: Hardware/OS recommendations for large databases (
  • From: William Yu
• Re: Perl DBD and an alarming problem
  • From: Craig A. James
• Re: Hardware/OS recommendations for large databases (
  • From: David Boreham
• Re: Hardware/OS recommendations for large databases (
  • From: Joshua Marsh
• weird performances problem
  • From: Guillaume Smet
• Re: Hardware/OS recommendations for large databases (
  • From: Joshua D. Drake
• Re: Hardware/OS recommendations for large databases (
  • From: William Yu
• unsubscribe
  • From: Josel Malixi
• Re: Hardware/OS recommendations for large databases (
  • From: David Boreham
• Re: Hardware/OS recommendations for large databases (
  • From: Merlin Moncure
• Re: Hardware/OS recommendations for large databases (
  • From: Alex Turner
• Re: Hardware/OS recommendations for large databases (
  • From: Alex Turner
• Re: Hardware/OS recommendations for large databases (
  • From: Alex Turner
• Re: Strange query plan invloving a view
  • From: Tom Lane
• Re: Help speeding up delete
  • From: Steinar H. Gunderson
• Re: Help speeding up delete
  • From: Scott Marlowe
• Re: [pgsql-www] Help speeding up delete
  • From: Magnus Hagander
• Re: [pgsql-www] Help speeding up delete
  • From: Steve Wampler
• Re: Help speeding up delete
  • From: Christopher Kings-Lynne
• Re: [pgsql-www] Help speeding up delete
  • From: Christopher Kings-Lynne
• Re: Hardware/OS recommendations for large databases (5TB)
  • From: Vivek Khera
• Re: Hardware/OS recommendations for large databases (
  • From: William Yu
• Re: Help speeding up delete
  • From: Steinar H. Gunderson
• Re: [pgsql-www] Help speeding up delete
  • From: Magnus Hagander
• Strange query plan invloving a view
  • From: Rich Doughty
• Re: Help speeding up delete
  • From: Christopher Kings-Lynne
• Re: Help speeding up delete
  • From: Christopher Kings-Lynne
• Re: Perl DBD and an alarming problem
  • From: Michael Fuhr
• Re: Perl DBD and an alarming problem
  • From: Greg Sabino Mullane
• Re: Help speeding up delete
  • From: Arjen van der Meijden
• PgPool and Postgresql sessions...
  • From: Cristian Prieto
• Re: Hardware/OS recommendations for large databases (5TB)
  • From: Claus Guttesen
• Re: Hardware/OS recommendations for large databases (
  • From: mudfoot
• Re: Hardware/OS recommendations for large databases
  • From: Ron
• Re: Hardware/OS recommendations for large databases (
  • From: Ron Mayer
• Perl DBD and an alarming problem
  • From: Craig A. James
• Re: Hardware/OS recommendations for large databases
  • From: Ron
• Re: Help speeding up delete
  • From: Steve Wampler
• Re: Hardware/OS recommendations for large databases (
  • From: Scott Marlowe
• Re: Help speeding up delete
  • From: Simon Riggs
• Re: Hardware/OS recommendations for large databases (5TB)
  • From: Vivek Khera
• Re: Hardware/OS recommendations for large databases (
  • From: Welty, Richard
• OT Re: Hardware/OS recommendations for large databases (
  • From: Douglas J. Trainor
• Re: Hardware/OS recommendations for large databases (
  • From: Matthew Nuzum
• Re: Hardware/OS recommendations for large databases (
  • From: Steinar H. Gunderson
• Re: Hardware/OS recommendations for large databases (
  • From: Matthew Nuzum
• Re: Hardware/OS recommendations for large databases (
  • From: Scott Marlowe
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases
  • From: Alex Turner
• Re: Hardware/OS recommendations for large databases (
  • From: Scott Marlowe
• Re: Hardware/OS recommendations for large databases (
  • From: Scott Marlowe
• Re: Hardware/OS recommendations for large databases (
  • From: Joshua D. Drake
• Re: Hardware/OS recommendations for large databases (
  • From: David Boreham
• Re: Hardware/OS recommendations for large databases (
  • From: Joshua D. Drake
• Re: Hardware/OS recommendations for large databases (
  • From: William Yu
• Re: Hardware/OS recommendations for large databases (
  • From: William Yu
• Re: Hardware/OS recommendations for large databases (
  • From: David Boreham
• Re: Hardware/OS recommendations for large databases (
  • From: Steve Wampler
• Re: Hardware/OS recommendations for large databases (
  • From: William Yu
• Re: Hardware/OS recommendations for large databases (
  • From: David Boreham
• Re: Hardware/OS recommendations for large databases (
  • From: Steve Wampler
• Re: Hardware/OS recommendations for large databases (
  • From: Alex Stapleton
• Re: Hardware/OS recommendations for large databases
  • From: Ron
• Re: Hardware/OS recommendations for large databases (
  • From: Joshua D. Drake
• Re: Hardware/OS recommendations for large databases ( 5TB)
  • From: William Yu
• Re: Hardware/OS recommendations for large databases (
  • From: William Yu
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Alex Turner
• Re: Hardware/OS recommendations for large databases (
  • From: Alex Turner
• Re: Hardware/OS recommendations for large databases ( 5TB)
  • From: James Mello
• Re: Too Many OR's?
  • From: Scott Marlowe
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Steve Wampler
• Too Many OR's?
  • From: Bill McGonigle
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: Hardware/OS recommendations for large databases ( 5TB)
  • From: William Yu
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Luke Lonergan
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases ( 5TB)
  • From: Adam Weisberg
• Re: Hardware/OS recommendations for large databases ( 5TB)
  • From: Merlin Moncure
• Re: Hardware/OS recommendations for large databases (
  • From: Michael Stone
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Hardware/OS recommendations for large databases (
  • From: Dave Cramer
• Re: Help speeding up delete
  • From: Steve Wampler
• Re: Hardware/OS recommendations for large databases (5TB)
  • From: Merlin Moncure
• Re: Hardware/OS recommendations for large databases (
  • From: Luke Lonergan
• Re: Help speeding up delete
  • From: Magnus Hagander
• Re: Hardware/OS recommendations for large databases (5TB)
  • From: Claus Guttesen
• Re: Help speeding up delete
  • From: Steve Wampler
• Re: Help speeding up delete
  • From: Scott Lamb
• Re: Help speeding up delete
  • From: Steve Wampler
• Re: Help speeding up delete
  • From: Joshua Marsh
• Re: Help speeding up delete
  • From: Steve Wampler
• Re: Postgres recovery time
  • From: David Boreham
• Hardware/OS recommendations for large databases (5TB)
  • From: Adam Weisberg
• Re: Help speeding up delete
  • From: Steve Wampler
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware Raid5 / Debian??
  • From: Dave Cramer
• Re: Help speeding up delete
  • From: Tom Lane
• Re: Help speeding up delete
  • From: Scott Lamb
• Help speeding up delete
  • From: Steve Wampler
• Postgres recovery time
  • From: Piccarello, James (James)
• Re: slow queries after ANALYZE
  • From: DW
• Re: 8.x index insert performance
  • From: Ron
• Re: 8.x index insert performance
  • From: Kelly Burkhart
• Re: IO Error
  • From: Tom Lane
• IO Error
  • From: Yves Vindevogel
• Re: slow queries after ANALYZE
  • From: hubert depesz lubaczewski
• Re: 8.x index insert performance
  • From: Kevin Grittner
• Re: 8.x index insert performance
  • From: Tom Lane
• Re: 8.x index insert performance
  • From: Kelly Burkhart
• Re: slow queries after ANALYZE
  • From: Tom Lane
• Re: slow queries after ANALYZE
  • From: DW
• Re: slow queries after ANALYZE
  • From: Tom Lane
• slow queries after ANALYZE
  • From: DW
• Re: same plan, add 1 condition, 1900x slower
  • From: Tom Lane
• Re: same plan, add 1 condition, 1900x slower
  • From: Mitchell Skinner
• Re: same plan, add 1 condition, 1900x slower
  • From: Tom Lane
• Re: same plan, add 1 condition, 1900x slower
  • From: Tom Lane
• Re: same plan, add 1 condition, 1900x slower
  • From: Mitch Skinner
• Re: same plan, add 1 condition, 1900x slower
  • From: Mitch Skinner
• Re: same plan, add 1 condition, 1900x slower
  • From: Tom Lane
• Re: same plan, add 1 condition, 1900x slower
  • From: Tom Lane
• Re: same plan, add 1 condition, 1900x slower
  • From: Richard Huxton
• Re: same plan, add 1 condition, 1900x slower
  • From: Mitch Skinner
• Re: Index Scan Costs versus Sort
  • From: Tom Lane
• Re: Index Scan Costs versus Sort
  • From: Charlie Savage
• Re: 8.x index insert performance
  • From: Tom Lane
• Re: 8.x index insert performance
  • From: Tom Lane
• Re: 8.x index insert performance
  • From: Tom Lane
• Re: 8.x index insert performance
  • From: Kelly Burkhart
• Re: 8.x index insert performance
  • From: Kelly Burkhart
• Re: Index Scan Costs versus Sort
  • From: Charlie Savage
• Re: Outer Join performance in PostgreSQL
  • From: Ashok Agrawal
• Re: Index Scan Costs versus Sort
  • From: Tom Lane
• Re: WAL sync behaviour
  • From: Steinar H. Gunderson
• Re: WAL sync behaviour
  • From: Tom Lane
• Re: same plan, add 1 condition, 1900x slower
  • From: Tom Lane
• Re: WAL sync behaviour
  • From: mark
• Index Scan Costs versus Sort
  • From: Charlie Savage
• same plan, add 1 condition, 1900x slower
  • From: Mitch Skinner
• Re: WAL sync behaviour
  • From: Scott Marlowe
• Re: WAL sync behaviour
  • From: Tom Lane
• Re: Sort performance on large tables
  • From: Alex Turner
• Re: Sort performance on large tables
  • From: Ron Peacetree
• Re: WAL sync behaviour
  • From: Michael Stone
• Re: WAL sync behaviour
  • From: Scott Marlowe
• Re: Some help on buffers and other performance tricks
  • From: Scott Marlowe
• Re: Some help on buffers and other performance tricks
  • From: Merlin Moncure
• Re: WAL sync behaviour
  • From: Michael Stone
• Re: Some help on buffers and other performance tricks
  • From: Frank Wiles
• Re: Some help on buffers and other performance tricks
  • From: Scott Marlowe
• Re: WAL sync behaviour
  • From: Steinar H. Gunderson
• Re: WAL sync behaviour
  • From: Richard Huxton
• WAL sync behaviour
  • From: Steinar H. Gunderson
• Re: (View and SQL) VS plpgsql
  • From: Nörder-Tuitje, Marcus
• Re: Some help on buffers and other performance tricks
  • From: Ron Peacetree
• Re: Some help on buffers and other performance tricks
  • From: Frank Wiles
• Re: Some help on buffers and other performance tricks
  • From: Frank Wiles
• Re: Some help on buffers and other performance tricks
  • From: Alvaro Herrera
• Re: Some help on buffers and other performance tricks
  • From: Alvaro Herrera
• Re: Outer Join performance in PostgreSQL
  • From: Stephan Szabo
• (View and SQL) VS plpgsql
  • From: Eric Lauzon
• Re: Sort performance on large tables
  • From: Ron Peacetree
• Re: Outer Join performance in PostgreSQL
  • From: Michael Alan Dorman
• Re: Some help on buffers and other performance tricks
  • From: Ron Peacetree
• Some help on buffers and other performance tricks
  • From: Yves Vindevogel
• Outer Join performance in PostgreSQL
  • From: Ashok Agrawal
• Re: Improving performance on multicolumn query
  • From: Jan Kesten
• Re: Sort performance on large tables
  • From: Charlie Savage
• Re: Improving performance on multicolumn query
  • From: Steinar H. Gunderson
• Re: Improving performance on multicolumn query
  • From: Christopher Kings-Lynne
• Re: Improving performance on multicolumn query
  • From: Steinar H. Gunderson
• Re: Improving performance on multicolumn query
  • From: Richard Huxton
• Improving performance on multicolumn query
  • From: Jan Kesten
• Re: Sort performance on large tables
  • From: Simon Riggs
• Re: Sort performance on large tables
  • From: Charlie Savage
• Re: Figuring out which command failed
  • From: Thomas F. O'Connell
• [no subject]
  • From: William Lai
• Re: Sort performance on large tables
  • From: Christopher Kings-Lynne
• Re: Sort performance on large tables
  • From: Charlie Savage
• Re: Sort performance on large tables
  • From: Tom Lane
• Re: Sort performance on large tables
  • From: Charlie Savage
• Re: Sort performance on large tables
  • From: Stephan Szabo
• Re: Sort performance on large tables
  • From: Luke Lonergan
• Re: Sort performance on large tables
  • From: Stephan Szabo
• Re: Sort performance on large tables
  • From: Marc Morin
• Re: Sort performance on large tables
  • From: Luke Lonergan
• Re: 8.1 iss
  • From: Mario Weilguni
• Re: Sort performance on large tables
  • From: Richard Huxton
• Sort performance on large tables
  • From: Charlie Savage
• Re: Expensive function and the optimizer
  • From: Tom Lane
• Expensive function and the optimizer
  • From: Craig A. James
• Re: Temporary Table
  • From: Andrew McMillan
• Re: Temporary Table
  • From: Jeff Frost
• Re: Temporary Table
  • From: Christopher Kings-Lynne
• Re: Temporary Table
  • From: Christopher Kings-Lynne
• Re: Temporary Table
  • From: Christian Paul B. Cosinas
• Re: Temporary Table
  • From: Christopher Kings-Lynne
• Re: Temporary Table
  • From: Joshua D. Drake
• Re: Temporary Table
  • From: Christian Paul B. Cosinas
• Re: Temporary Table
  • From: Christian Paul B. Cosinas
• Re: Temporary Table
  • From: Ralph Mason
• Figuring out which command failed
  • From: Ralph Mason
• Re: Index + mismatching datatypes [WAS: index on custom
  • From: Neil Conway
• Index + mismatching datatypes [WAS: index on custom function; explain]
  • From: Enrico Weigelt
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Andreas Pflug
• Re: 8.1 iss
  • From: PostgreSQL
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware Raid5 / Debian??
  • From: Alex Turner
• Re: Temporary Table
  • From: Alvaro Herrera
• Re: Performance problem with pg8.0
  • From: Richard Huxton
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Dave Page
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Dave Page
• FW: Used Memory
  • From: Christian Paul B. Cosinas
• Temporary Table
  • From: Christian Paul B. Cosinas
• Re: 8.1 iss
  • From: Dennis Bjorklund
• Re: Used Memory
  • From: Christian Paul B. Cosinas
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Christopher Kings-Lynne
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: [PERFORM] 8.1 iss
  • From: Luke Lonergan
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Tom Lane
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware
  • From: Joost Kraaijeveld
• Re: 8.1 iss
  • From: Greg Stark
• Performance problem with pg8.0
  • From: Jeroen van Iddekinge
• Re: Performance PG 8.0 on dual opteron / 4GB / 3ware Raid5 / Debian??
  • From: Tom Lane
• Re: 8.1 iss
  • From: Tom Lane
• Performance PG 8.0 on dual opteron / 4GB / 3ware Raid5 / Debian??
  • From: Joost Kraaijeveld
• 8.1 iss
  • From: PostgreSQL
• Re: [HACKERS] insert performance for win32
  • From: Simon Riggs
• Re: insert performance for win32
  • From: Qingqing Zhou
• Re: [HACKERS] insert performance for win32
  • From: Magnus Hagander
• Re: insert performance for win32
  • From: Qingqing Zhou
• Re: [HACKERS] insert performance for win32
  • From: Bruce Momjian
• Re: insert performance for win32
  • From: Magnus Hagander
• Re: [HACKERS] insert performance for win32
  • From: Tom Lane
• Re: insert performance for win32
  • From: Bruce Momjian
• Re: insert performance for win32
  • From: Tom Lane
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Tom Lane
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: Searching union views not using indices
  • From: Tom Lane
• Re: insert performance for win32
  • From: Tom Lane
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: Searching union views not using indices
  • From: Michal Taborsky
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Tom Lane
• Re: Searching union views not using indices
  • From: Tom Lane
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Tom Lane
• Re: Searching union views not using indices
  • From: Michael Fuhr
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: Searching union views not using indices
  • From: Merlin Moncure
• Re: Searching union views not using indices
  • From: Richard Huxton
• Re: insert performance for win32
  • From: Tom Lane
• Searching union views not using indices
  • From: Michal Taborsky
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Qingqing Zhou
• Re: insert performance for win32
  • From: Tom Lane
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Qingqing Zhou
• Re: insert performance for win32
  • From: Qingqing Zhou
• Encoding on 8.0.4
  • From: Don Drake
• Re: insert performance for win32
  • From: Qingqing Zhou
• Re: insert performance for win32
  • From: Magnus Hagander
• Re: insert performance for win32
  • From: Qingqing Zhou
• Re: insert performance for win32
  • From: Magnus Hagander
• Re: insert performance for win32
  • From: Qingqing Zhou
• Re: insert performance for win32
  • From: Magnus Hagander
• Re: Sorted union
  • From: Kevin Grittner
• Re: insert performance for win32
  • From: Magnus Hagander
• Re: Sorted union
  • From: Scott Lamb
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: Sorted union
  • From: Merlin Moncure
• Re: Sorted union
  • From: Kevin Grittner
• Re: Sorted union
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: Sorted union
  • From: Scott Lamb
• Re: Sorted union
  • From: Merlin Moncure
• Re: Sorted union
  • From: Scott Lamb
• Re: Function with table%ROWTYPE globbing
  • From: Merlin Moncure
• Function with table%ROWTYPE globbing
  • From: Sven Willenberger
• Re: Sorted union
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Qingqing Zhou
• Re: Sorted union
  • From: Scott Lamb
• Sorted union
  • From: Scott Lamb
• Re: Trigger Rowsets
  • From: Jim C. Nasby
• Trigger Rowsets
  • From: Ralph Mason
• Re: 8.x index insert performance
  • From: Greg Stark
• Re: improvise callbacks in plpgsql
  • From: Merlin Moncure
• Re: improvise callbacks in plpgsql
  • From: Merlin Moncure
• Performance difference between sql and pgsql function...
  • From: Cristian Prieto
• Re: insert performance for win32
  • From: Tom Lane
• Re: insert performance for win32
  • From: Marc Cousin
• Re: pgbench results interpretation?
  • From: Joost Kraaijeveld
• Re: 8.1beta3 performance
  • From: Tom Lane
• Re: insert performance for win32
  • From: Magnus Hagander
• Re: improvise callbacks in plpgsql
  • From: Merlin Moncure
• Re: insert performance for win32
  • From: Merlin Moncure
• Re: pgbench results interpretation?
  • From: Gavin Sherry
• Re: 8.1beta3 performance
  • From: PostgreSQL
• Re: performance of implicit join vs. explicit conditions on inet queries?
  • From: Tom Lane
• Re: performance of implicit join vs. explicit conditions on inet queries?
  • From: Qingqing Zhou
• Re: Joining views disables indexes?
  • From: Tom Lane
• Re: Joining views disables indexes?
  • From: Steinar H. Gunderson
• Re: Joining views disables indexes?
  • From: Jim C. Nasby
• Joining views disables indexes?
  • From: Mitch Pirtle
• Re: solutions for new Postgresql application testing
  • From: Geoffrey
• Re: improvise callbacks in plpgsql
  • From: Jim C. Nasby
• Re: improvise callbacks in plpgsql
  • From: Merlin Moncure
• Re: improvise callbacks in plpgsql
  • From: Tom Lane
• Re: solutions for new Postgresql application testing
  • From: Merlin Moncure
• improvise callbacks in plpgsql
  • From: Merlin Moncure
• Re: 8.1beta3 performance
  • From: Tom Lane
• Re: 8.1beta3 performance
  • From: Dave Page
• Re: 8.x index insert performance
  • From: Ron Peacetree
• Re: 8.1beta3 performance
  • From: Jon Brisbin
• solutions for new Postgresql application testing
  • From: Geoffrey
• Re: 8.x index insert performance
  • From: Tom Lane
• Re: 8.x index insert performance
  • From: Kelly Burkhart
• Re: pgbench results interpretation?
  • From: Joost Kraaijeveld
• Re: pgbench results interpretation?
  • From: Gavin Sherry
• pgbench results interpretation?
  • From: Joost Kraaijeveld
• Re: "Group By " index usage
  • From: Alban Medici (NetCentrex)
• Re: VACUUM ANALYZE downgrades performance
  • From: Thomas Swan
• Re: VACUUM ANALYZE downgrades performance
  • From: Mike Rylander
• VACUUM ANALYZE downgrades performance
  • From: Dmitry Karasik
• Re: Postgres vs. DSpam
  • From: Jim C. Nasby
• Re: [dspam-users] Postgres vs. MySQL
  • From: Christopher Browne
• Re: [dspam-users] Postgres vs. MySQL
  • From: Lionel Bouton
• Re: [dspam-users] Postgres vs. MySQL
  • From: Casey Allen Shobe
• Re: time to stop tuning?
  • From: Rod Taylor
• Re: [dspam-users] Postgres vs. MySQL
  • From: Clifton Royston
• Re: Postgres backend using huge amounts of ram
  • From: Gary Doades
• Re: Postgres backend using huge amounts of ram
  • From: Tom Lane
• Re: time to stop tuning?
  • From: David Parker
• Re: time to stop tuning?
  • From: Tom Lane
• Re: time to stop tuning?
  • From: Rod Taylor
• time to stop tuning?
  • From: David Parker
• Re: Postgres backend using huge amounts of ram
  • From: Richard Huxton
• Re: [GENERAL] HELP speed up my Postgres
  • From: Jerome Macaranas
• Re: Postgres vs. DSpam
  • From: Neil Conway
• Re: Postgres vs. DSpam
  • From: Andrew McMillan
• Postgres backend using huge amounts of ram
  • From: Gary Doades
• Re: Postgres vs. MySQL
  • From: Dave Cramer
• Re: HELP speed up my Postgres
  • From: Christopher Kings-Lynne
• Re: HELP speed up my Postgres
  • From: Klint Gore
• Re: HELP speed up my Postgres
  • From: Tom Lane
• Re: HELP speed up my Postgres
  • From: JM
• Re: HELP speed up my Postgres
  • From: Vishal Kashyap @ [SaiHertz]
• HELP speed up my Postgres
  • From: JM
• Re: Postgres vs. MySQL
  • From: Steinar H. Gunderson
• Re: Slow execution time when querying view with WHERE clause
  • From: Mike Mascari
• Re: FW: Index usage
  • From: gnari
• Hardware purchase question
  • From: Bo Stewart
• Re: "Group By " index usage
  • From: Tom Lane
• "Group By " index usage
  • From: sdfasdfas sdfasdfs
• Re: [PERFORMANCE] Big number of schemas (3500) into a single database
  • From: Jaime Casanova
• Re: Postgres vs. MySQL
  • From: Steinar H. Gunderson
• Re: memcached and PostgreSQL
  • From: Jim C. Nasby
• Re: Postgres vs. MySQL
  • From: Joshua D. Drake
• Re: Data type to use for primary key
  • From: Alexandre Leclerc
• Re: Postgres vs. MySQL
  • From: Christian Fowler
• Re: Postgres vs. MySQL
  • From: Richard Huxton
• Re: Postgres vs. MySQL
  • From: Steinar H. Gunderson
• Postgres vs. MySQL
  • From: Evilio del Rio
• Re: FW: FW: Index usage
  • From: Richard Huxton
• Re: FW: FW: Index usage
  • From: BBI Edwin Punzalan
• Re: FW: FW: Index usage
  • From: Richard Huxton
• Re: FW: Index usage
  • From: BBI Edwin Punzalan
• Re: FW: Index usage
  • From: gnari
• Re: Data type to use for primary key
  • From: Greg Stark
• FW: FW: Index usage
  • From: BBI Edwin Punzalan
• Re: FW: Index usage
  • From: Leeuw van der, Tim
• Re: Data type to use for primary key
  • From: Tom Lane
• Re: Data type to use for primary key
  • From: Greg Stark
• FW: Index usage
  • From: BBI Edwin Punzalan
• Re: Slow execution time when querying view with WHERE clause
  • From: Tom Lane
• Re: Slow execution time when querying view with WHERE clause
  • From: Tom Lane
• Re: Slow execution time when querying view with WHERE clause
  • From: Jaime Casanova
• Re: [pgsql-hackers-win32] scalability issues on win32
  • From: Bruce Momjian
• Re: Slow execution time when querying view with WHERE clause
  • From: Mike Mascari
• Re: memcached and PostgreSQL
  • From: Sean Chittenden
• Re: [pgsql-hackers-win32] scalability issues on win32
  • From: Dave Page
• Re: Slow execution time when querying view with WHERE clause
  • From: Tom Lane
• Re: Some quick Opteron 32-bit/64-bit results
  • From: Cott Lang
• Re: [pgsql-hackers-win32] scalability issues on win32
  • From: Merlin Moncure
• Re: Data type to use for primary key
  • From: Pierre-Frédéric Caillaud
• Re: Data type to use for primary key
  • From: Alexandre Leclerc
• Re: [pgsql-hackers-win32] scalability issues on win32
  • From: Magnus Hagander
• Re: [pgsql-hackers-win32] scalability issues on win32
  • From: Bruce Momjian
• Re: Data type to use for primary key
  • From: Peter Darley
• Re: [pgsql-hackers-win32] scalability issues on win32
  • From: Merlin Moncure
• Re: [pgsql-hackers-win32] scalability issues on win32
  • From: Dave Page
• Re: [pgsql-hackers-win32] scalability issues on win32
  • From: Reini Urban
• Re: Data type to use for primary key
  • From: Pierre-Frédéric Caillaud
• Re: Data type to use for primary key
  • From: Josh Berkus
• Re: [pgsql-hackers-win32] scalability issues on win32
  • From: Bruce Momjian
• Re: memcached and PostgreSQL
  • From: Bruce Momjian
• Re: Data type to use for primary key
  • From: Rod Taylor
• Re: Data type to use for primary key
  • From: Josh Berkus
• Re: Data type to use for primary key
  • From: Alexandre Leclerc
• Re: scalability issues on win32
  • From: Pierre-Frédéric Caillaud
• Re: Data type to use for primary key
  • From: Pierre-Frédéric Caillaud
• scalability issues on win32
  • From: Merlin Moncure
• Re: Slow execution time when querying view with WHERE clause
  • From: Mike Mascari
• Slow execution time when querying view with WHERE clause
  • From: Mike Mascari
• Data type to use for primary key
  • From: Alexandre Leclerc
• Re: help needed -- sequential scan problem
  • From: gnari
• Re: help needed -- sequential scan problem
  • From: sarlav kumar
• Re: help needed -- sequential scan problem
  • From: Josh Berkus
• Re: help needed -- sequential scan problem
  • From: sarlav kumar
• Re: Query Performance and IOWait
  • From: Anjan Dave