• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Mailing Lists
  • Subscribe
  • User lists
    • pgsql-admin
    • pgsql-advocacy
    • pgsql-announce
    • pgsql-bugs
    • pgsql-docs
    • pgsql-cygwin
    • pgsql-general
    • pgsql-interfaces
    • pgsql-jdbc
    • pgsql-jobs
    • pgsql-novice
    • pgsql-odbc
    • pgsql -performance
    • pgsql-php
    • pgsql-ports
    • pgsql-sql
  • Developer lists
  • Regional lists
  • Project lists
  • User groups
  • Inactive lists
• IRC
• In The Real World
• International Sites
• Propaganda
• Resources
• Weekly News

pgsql-performance 2007-02 Chronological Index (1/2)

• Thread Index
• [Prev Page]
• [Next Page]

• 01 March 2007
  • Re: Two hard drives --- what to do with them? Bruno Wolff III
  • Re: Two hard drives --- what to do with them? Bruno Wolff III
  • Re: Two hard drives --- what to do with them? Bruno Wolff III
• 28 February 2007
  • Re: Upgraded to 8.2.3 --- still having performance issues Carlos Moreno
  • Re: Upgraded to 8.2.3 --- still having performance issues Carlos Moreno
  • Re: Upgraded to 8.2.3 --- still having performance issues Rodrigo Gonzalez
  • Re: Upgraded to 8.2.3 --- still having performance issues Carlos Moreno
  • Re: Upgraded to 8.2.3 --- still having performance issues Tom Lane
  • Upgraded to 8.2.3 --- still having performance issues Carlos Moreno
  • Re: Writting a "search engine" for a pgsql DB Dave Page
  • Re: Writting a "search engine" for a pgsql DB Oleg Bartunov
  • Re: Writting a "search engine" for a pgsql DB Dave Page
  • Re: Writting a "search engine" for a pgsql DB Steinar H. Gunderson
  • Re: Writting a "search engine" for a pgsql DB Dave Page
  • Re: Writting a "search engine" for a pgsql DB Magnus Hagander
• 27 February 2007
  • Re: Opinions on Raid Geoff Tolley
  • Re: Writting a "search engine" for a pgsql DB Charles Sprickman
  • Re: Writting a "search engine" for a pgsql DB Chris
  • Re: Two hard drives --- what to do with them? Scott Marlowe
  • Re: Two hard drives --- what to do with them? Jeff Davis
  • Re: Opinions on Raid Scott Marlowe
  • Re: [kris(at)obsecurity(dot)org: Anyone interested in improving postgresql scaling?] Tom Lane
  • Re: Two hard drives --- what to do with them? Shane Ambler
  • [kris(at)obsecurity(dot)org: Anyone interested in improving postgresql scaling?] Jim C. Nasby
  • [kris(at)obsecurity(dot)org: Progress on scaling of FreeBSD on 8 CPU systems] Jim C. Nasby
  • Re: Postgres performance Linux vs FreeBSD Andrew - Supernews
  • Re: Opinions on Raid Scott Marlowe
  • Re: Opinions on Raid mark
  • Re: Opinions on Raid Ron
  • Re: Two hard drives --- what to do with them? Ben
  • Re: Opinions on Raid Stefan Kaltenbrunner
  • Re: Writting a "search engine" for a pgsql DB Dave Page
  • Opinions on Raid Joe Uhl
  • Re: Writting a "search engine" for a pgsql DB Magnus Hagander
  • Re: Two hard drives --- what to do with them? Peter Kovacs
  • Re: Two hard drives --- what to do with them? Shane Ambler
  • Re: Two hard drives --- what to do with them? Jeff Davis
  • Re: Two hard drives --- what to do with them? Peter Kovacs
• 26 February 2007
  • Re: Two hard drives --- what to do with them? Jeff Davis
  • Re: Writting a "search engine" for a pgsql DB Charles Sprickman
  • Re: Vacuumdb - Max_FSM_Pages Problem. Ron
  • Re: Writting a "search engine" for a pgsql DB Jeff Davis
  • Re: Writting a "search engine" for a pgsql DB Mark Stosberg
  • Re: Writting a "search engine" for a pgsql DB Madison Kelly
  • Re: Writting a "search engine" for a pgsql DB Mark Stosberg
  • Re: Writting a "search engine" for a pgsql DB Magnus Hagander
  • Re: Writting a "search engine" for a pgsql DB Madison Kelly
  • Re: [JDBC] does prepareThreshold work? forced to use old driver Gene
  • Re: Writting a "search engine" for a pgsql DB Joshua D. Drake
  • Re: Writting a "search engine" for a pgsql DB Mark Stosberg
  • Re: [JDBC] does prepareThreshold work? forced to use old driver Dave Cramer
  • Re: low memory usage reported by 'top' indicates poor tuning? Mark Stosberg
  • Re: low memory usage reported by 'top' indicates poor tuning? Joshua D. Drake
  • Re: Writting a "search engine" for a pgsql DB Joshua D. Drake
  • low memory usage reported by 'top' indicates poor tuning? Mark Stosberg
  • Re: [JDBC] does prepareThreshold work? forced to use old driver Kris Jurka
  • Writting a "search engine" for a pgsql DB Madison Kelly
  • does prepareThreshold work? forced to use old driver Gene
  • Re: Vacuumdb - Max_FSM_Pages Problem. Peter Childs
  • Vacuumdb - Max_FSM_Pages Problem. Pallav Kalva
  • Re: Server Startup Error Richard Huxton
  • Re: Server Startup Error Rodrigo Gonzalez
  • Re: Server Startup Error Richard Huxton
  • Re: Server Startup Error Gauri Kanekar
  • Re: Server Startup Error Rodrigo Gonzalez
  • Server Startup Error Gauri Kanekar
  • Re: pg_trgm performance Oleg Bartunov
  • Re: pg_trgm performance Guillaume Smet
  • Re: pg_trgm performance Oleg Bartunov
  • Re: pg_trgm performance Guillaume Smet
  • Re: Query Planner Steinar H. Gunderson
  • Query Planner Gauri Kanekar
  • Re: Very slow bytea data extraction Richard Huxton
  • invalid page header in block 428 of relation "pg_attribute" ashok(at)kalculate(dot)com
• 25 February 2007
  • Re: Two hard drives --- what to do with them? Peter Kovacs
  • Re: Two hard drives --- what to do with them? Alexander Staubo
  • Re: Two hard drives --- what to do with them? Tom Lane
  • Two hard drives --- what to do with them? Carlos Moreno
• 24 February 2007
  • Re: which Xeon processors don't have the context switching problem Joshua D. Drake
  • Re: pg_trgm performance Steinar H. Gunderson
  • Re: which Xeon processors don't have the context switching problem Geoffrey
  • Re: pg_trgm performance Guillaume Smet
  • Re: which Xeon processors don't have the context switching problem Magnus Hagander
  • Re: pg_trgm performance Steinar H. Gunderson
• 23 February 2007
  • Re: pg_trgm performance Guillaume Smet
  • Re: long checkpoint_timeout Jim C. Nasby
  • Re: which Xeon processors don't have the context switching problem Guillaume Smet
  • Re: which Xeon processors don't have the context switching problem Guillaume Smet
  • Re: which Xeon processors don't have the context switching problem Geoffrey
  • Re: which Xeon processors don't have the context switching problem Joshua D. Drake
  • Re: which Xeon processors don't have the context switching problem Geoffrey
  • Re: which Xeon processors don't have the context switching problem Josh Berkus
  • Re: long checkpoint_timeout Jeff Davis
  • Re: long checkpoint_timeout Jim C. Nasby
  • Re: which Xeon processors don't have the context switching problem Steinar H. Gunderson
  • Re: which Xeon processors don't have the context switching problem Alvaro Herrera
  • Re: which Xeon processors don't have the context switching problem Steinar H. Gunderson
  • Re: which Xeon processors don't have the context switching problem Claus Guttesen
  • which Xeon processors don't have the context switching problem Geoffrey
  • long checkpoint_timeout Jeff Davis
  • Re: Recommended Initial Settings Bill Moran
  • Re: Very slow bytea data extraction msmbarabino(at)virgilio(dot)it
  • Re: Very slow bytea data extraction msmbarabino(at)virgilio(dot)it
  • Re: Recommended Initial Settings Jim C. Nasby
  • Re: Using the 8.2 autovacuum values with 8.1 Jim C. Nasby
  • Re: Recommended Initial Settings Richard Huxton
  • Re: Recommended Initial Settings Campbell, Lance
  • Re: R: Very slow bytea data extraction Merlin Moncure
  • Re: Recommended Initial Settings Richard Huxton
  • Recommended Initial Settings Campbell, Lance
  • Re: R: Very slow bytea data extraction Richard Huxton
  • R: Very slow bytea data extraction msmbarabino(at)virgilio(dot)it
  • Re: Very slow bytea data extraction Richard Huxton
  • Very slow bytea data extraction msmbarabino(at)virgilio(dot)it
  • Re: Using the 8.2 autovacuum values with 8.1 Csaba Nagy
  • Re: slow update on 1M rows (worse with indexes) ismo . tuononen
• 22 February 2007
  • Using the 8.2 autovacuum values with 8.1 Mark Stosberg
  • Re: Vacuum full very slow due to nonremovable dead rows...What makes the dead rows non-removable? Steinar H. Gunderson
  • Vacuum full very slow due to nonremovable dead rows...What makes the dead rows non-removable? Barbara Cosentino
  • Re: slow update on 1M rows (worse with indexes) Joshua D. Drake
  • Re: slow update on 1M rows (worse with indexes) Steinar H. Gunderson
  • slow update on 1M rows (worse with indexes) Gabriel Biberian
  • Re: Disable result buffering to frontend clients Richard Huxton
  • Disable result buffering to frontend clients Konstantinos Krikellas
• 21 February 2007
  • Re: How to avoid vacuuming a huge logging table D'Arcy J.M. Cain
  • Re: How to avoid vacuuming a huge logging table Greg Sabino Mullane
  • Re: General advice on user functions Dan Harris
  • Re: Postgres performance Linux vs FreeBSD Mark Kirkwood
  • Re: Auto-Vacuum in 8.1 was ineffective for me. 8.2 may work better? Alvaro Herrera
  • Re: Auto-Vacuum in 8.1 was ineffective for me. 8.2 may work better? Matthew T. O'Connor
  • Re: Auto-Vacuum in 8.1 was ineffective for me. 8.2 may work better? Mark Stosberg
  • Re: General advice on user functions Albert Cervera Areny
  • Re: General advice on user functions Merlin Moncure
  • Re: Postgres performance Linux vs FreeBSD Dimitri Fontaine
  • Re: How to avoid vacuuming a huge logging table Greg Sabino Mullane
  • Re: Auto-Vacuum in 8.1 was ineffective for me. 8.2 may work better? Alvaro Herrera
  • Auto-Vacuum in 8.1 was ineffective for me. 8.2 may work better? Mark Stosberg
  • General advice on user functions Dan Harris
  • How to avoid vacuuming a huge logging table Mark Stosberg
  • Re: How to debug performance problems Mark Stosberg
  • Re: How to debug performance problems Ray Stell
  • Re: How to debug performance problems Craig A. James
  • Re: How to debug performance problems Ray Stell
  • Re: Postgres performance Linux vs FreeBSD Bill Moran
  • Re: Postgres performance Linux vs FreeBSD Merlin Moncure
  • Postgres performance Linux vs FreeBSD Jacek Zaręba
  • Re: slow subselects Marko Niinimaki
• 20 February 2007
  • Re: SELECT performance problem Dave Dutcher
  • Re: SELECT performance problem Jeff Frost
  • SELECT performance problem Glenn Sullivan
  • Re: Query Optimization Jim C. Nasby
  • Re: slow subselects Tom Lane
  • Re: slow subselects ismo . tuononen
  • slow subselects Marko Niinimaki
  • Re: Query Optimization Tom Lane
• 19 February 2007
  • Re: How to debug performance problems Scott Marlowe
  • Re: How to debug performance problems Jeff Davis
  • Re: How to debug performance problems Craig A. James
  • Query Optimization Reinhard Vicinus
  • How to debug performance problems Andreas Tille
• 16 February 2007
  • Re: Not Picking Index Tom Lane
  • Re: reindex vs 'analyze' Mark Stosberg
  • Re: Not Picking Index George Pavlov
  • Re: Not Picking Index Steinar H. Gunderson
  • Re: Proximity query with GIST and row estimation Guillaume Smet
  • Re: Not Picking Index Brad Nicholson
  • Fwd: Not Picking Index Mike Gargano
  • Re: Not Picking Index Tom Lane
  • Re: Not Picking Index Alvaro Herrera
  • Re: Not Picking Index Gauri Kanekar
  • Re: Not Picking Index Michael Fuhr
  • Not Picking Index Gauri Kanekar
  • Re: Benchmarking PGSQL? Krishna Kumar
  • Re: Question about Bitmap Heap Scan/BitmapAnd Guillaume Smet
• 15 February 2007
  • Re: Question about Bitmap Heap Scan/BitmapAnd Guillaume Smet
  • strange issue for certain queries Mike Gargano
  • Re: Slow query with 'or' clause philippe
  • Re: Question about Bitmap Heap Scan/BitmapAnd Tom Lane
  • Re: Question about Bitmap Heap Scan/BitmapAnd Alvaro Herrera
  • Re: Proximity query with GIST and row estimation Guillaume Smet

• Thread Index
• [Prev Page]
• [Next Page]