• 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 2008-03 Chronological Index (1/3)

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

• 01 April 2008
  • Re: Performance Implications of Using Exceptions Robins Tharakan
  • Re: Performance Implications of Using Exceptions Ravi Chemudugunta
  • Re: Performance Implications of Using Exceptions Stephen Denne
  • Re: Performance Implications of Using Exceptions Stephen Frost
  • Performance Implications of Using Exceptions Ravi Chemudugunta
• 31 March 2008
  • Re: POSIX file updates Greg Smith
  • Re: POSIX file updates James Mansion
  • Re: POSIX file updates James Mansion
  • Re: POSIX file updates James Mansion
  • Re: POSIX file updates Mark Mielke
  • POSIX file updates James Mansion
  • optimizing query performance Frits Hoogland
  • Re: Bad prepare performance Cédric Villemain
  • Bad prepare performance Martin Kjeldsen
  • Re: Planning a new server - help needed Guy Rouillier
• 30 March 2008
  • Re: Planning a new server - help needed Craig Ringer
  • Re: Planning a new server - help needed Greg Smith
• 29 March 2008
  • Re: Planning a new server - help needed Peter Eisentraut
  • Re: Planning a new server - help needed James Mansion
  • Re: Planning a new server - help needed PFC
  • Re: Planning a new server - help needed James Mansion
  • Re: Planning a new server - help needed Weinzierl Stefan
• 28 March 2008
  • Re: Planning a new server - help needed Dan Harris
  • Re: Planning a new server - help needed Greg Smith
  • Re: using like in a prepare doesnt' use the right index Gavin Sherry
  • Re: Planning a new server - help needed Laszlo Nagy
  • Re: Planning a new server - help needed Reko Turja
  • Re: Planning a new server - help needed Claus Guttesen
  • Planning a new server - help needed Laszlo Nagy
  • Re: vacuum in Postgresql 8.0.x slowing down the database Vinubalaji Gopal
• 27 March 2008
  • using like in a prepare doesnt' use the right index Dave Cramer
  • Re: "Slow" query or just "Bad hardware"? Alvaro Herrera
  • Re: "Slow" query or just "Bad hardware"? Luke Lonergan
  • Re: postgresql is slow with larger table even it is in RAM Luke Lonergan
  • Re: "Slow" query or just "Bad hardware"? Bill Moran
  • Re: "Slow" query or just "Bad hardware"? PFC
  • Re: "Slow" query or just "Bad hardware"? PFC
  • Re: "Slow" query or just "Bad hardware"? Matthew
  • "Slow" query or just "Bad hardware"? Jesper Krogh
  • Re: how can a couple of expensive queries drag my system down? Erik Jones
  • Re: how can a couple of expensive queries drag my system down? Scott Marlowe
  • Re: how can a couple of expensive queries drag my system down? Shane Ambler
• 26 March 2008
  • Re: postgresql is slow with larger table even it is in RAM Peter Koczan
  • Re: how can a couple of expensive queries drag my system down? PFC
  • Re: how can a couple of expensive queries drag my system down? Scott Marlowe
  • Re: how can a couple of expensive queries drag my system down? Alan Hodgson
  • Re: vacuum in Postgresql 8.0.x slowing down the database Joshua D. Drake
  • vacuum in Postgresql 8.0.x slowing down the database Vinubalaji Gopal
  • how can a couple of expensive queries drag my system down? p prince
  • Query Optimization Gopinath Narasimhan
  • Re: 1-/2-dimensional indexes for common columns, rationale? PFC
  • Re: 1-/2-dimensional indexes for common columns, rationale? Craig Ringer
  • Re: 1-/2-dimensional indexes for common columns, rationale? A. Kretschmer
  • Re: 1-/2-dimensional indexes for common columns, rationale? Marinos Yannikos
  • Re: 1-/2-dimensional indexes for common columns, rationale? Matthew
  • Re: 1-/2-dimensional indexes for common columns, rationale? A. Kretschmer
  • 1-/2-dimensional indexes for common columns, rationale? Marinos Yannikos
  • Re: what is the maximum number of rows in a table in postgresql 8.1 Matthew
• 25 March 2008
  • Preparing statements on connection startup PFC
  • Re: postgresql is slow with larger table even it is in RAM Chris Browne
  • Re: postgresql is slow with larger table even it is in RAM sathiya psql
  • Re: postgresql is slow with larger table even it is in RAM Luke Lonergan
  • Re: postgresql is slow with larger table even it is in RAM Bill Moran
  • Re: what is the maximum number of rows in a table in postgresql 8.1 Bill Moran
  • Re: PostgreSQL NetApp and NFS Jurgen Haan
  • Re: postgresql is slow with larger table even it is in RAM sathiya psql
  • Re: what is the maximum number of rows in a table in postgresql 8.1 Ivan Voras
  • Re: postgresql is slow with larger table even it is in RAM Bill Moran
  • Re: what is the maximum number of rows in a table in postgresql 8.1 Craig Ringer
  • Re: what is the maximum number of rows in a table in postgresql 8.1 sathiya psql
  • Re: what is the maximum number of rows in a table in postgresql 8.1 Craig Ringer
  • Re: increasing shared buffer slow downs query performance. Pavan Deolasee
  • Re: what is the maximum number of rows in a table in postgresql 8.1 sathiya psql
  • Re: what is the maximum number of rows in a table in postgresql 8.1 Alvaro Herrera
  • Re: postgresql is slow with larger table even it is in RAM Alvaro Herrera
  • Re: what is the maximum number of rows in a table in postgresql 8.1 sathiya psql
  • Re: what is the maximum number of rows in a table in postgresql 8.1 Harald Armin Massa
  • what is the maximum number of rows in a table in postgresql 8.1 sathiya psql
  • Re: postgresql is slow with larger table even it is in RAM Craig Ringer
  • Re: postgresql is slow with larger table even it is in RAM hubert depesz lubaczewski
  • Re: postgresql is slow with larger table even it is in RAM sathiya psql
  • postgresql is slow with larger table even it is in RAM sathiya psql
  • Re: Planning hot/live backups? Matthew T. O'Connor
  • Re: slow pg_connect() Chris
  • Re: waiting for harddisk Scott Marlowe
• 24 March 2008
  • Re: Planning hot/live backups? Miguel Arroz
  • Re: Planning hot/live backups? Steve Poe
  • Re: Planning hot/live backups? Matthew T. O'Connor
  • Re: Planning hot/live backups? Tom Lane
  • Re: Planning hot/live backups? paul rivers
  • Re: Planning hot/live backups? Matthew T. O'Connor
  • Re: Planning hot/live backups? Campbell, Lance
  • Planning hot/live backups? Steve Poe
  • Re: Turn correlated in subquery into join Tom Lane
  • Re: waiting for harddisk PFC
  • waiting for harddisk petchimuthu lingam
  • Re: slow pg_connect() Thomas Pundt
  • Re: slow pg_connect() Tommy Gildseth
  • Re: increasing shared buffer slow downs query performance. Andreas Kretschmer
  • increasing shared buffer slow downs query performance. petchimuthu lingam
  • Re: slow pg_connect() vincent
  • Re: slow pg_connect() Craig Ringer
  • Re: slow pg_connect() Craig Ringer
  • Turn correlated in subquery into join Dennis Bjorklund
  • slow pg_connect() firerox
• 23 March 2008
  • Re: Views and functions returning sets of records Tom Lane
  • Re: Views and functions returning sets of records Giorgio Valoti
• 22 March 2008
  • Re: Views and functions returning sets of records Andreas Kretschmer
  • Re: Views and functions returning sets of records Tom Lane
  • Re: Views and functions returning sets of records Andreas Kretschmer
  • Views and functions returning sets of records Giorgio Valoti
  • Re: Having MANY MANY empty columns in database sathiya psql
  • Re: Having MANY MANY empty columns in database Craig Ringer
  • Having MANY MANY empty columns in database sathiya psql
  • Re: Linux/PostgreSQL scalability issue - problem with 8 cores Bruce Momjian
• 21 March 2008
  • Re: PostgreSQL NetApp and NFS Bruce Momjian
  • Re: PG writes a lot to the disk Bill Moran
  • Re: PG writes a lot to the disk Laurent Raufaste
  • Re: PG writes a lot to the disk Gregory Stark
  • Re: PostgreSQL NetApp and NFS Gregory Stark
  • Re: PG writes a lot to the disk Laurent Raufaste
  • Re: PostgreSQL NetApp and NFS Dawid Kuroczko
  • Re: PostgreSQL NetApp and NFS Tom Lane
  • Re: PostgreSQL NetApp and NFS Bruce Momjian
• 20 March 2008
  • Re: PostgreSQL NetApp and NFS Tom Lane
  • Re: PostgreSQL NetApp and NFS Frits Hoogland
  • Re: PostgreSQL NetApp and NFS Woody Woodring
  • Re: PG writes a lot to the disk Kris Jurka
  • Re: PostgreSQL NetApp and NFS Bruce Momjian
  • PostgreSQL NetApp and NFS Chris Hoover
  • Re: PG writes a lot to the disk Tom Lane
  • Re: PG writes a lot to the disk Bill Moran
  • Re: PG writes a lot to the disk Albe Laurenz
  • Re: PG writes a lot to the disk Laurent Raufaste
  • Re: Anyone using a SAN? Peter Koczan
• 19 March 2008
  • Windows XP 64 bit Campbell, Lance
  • Re: PG writes a lot to the disk Albe Laurenz
  • Re: PG writes a lot to the disk Greg Smith
  • Re: question on TRUNCATE vs VACUUM FULL Bill Moran
  • Re: PG writes a lot to the disk Bill Moran
  • Re: question on TRUNCATE vs VACUUM FULL Mark Steben
  • Re: What is the best way to storage music files in Postgresql Gregory Youngblood
  • Re: question on TRUNCATE vs VACUUM FULL Alvaro Herrera
  • Re: question on TRUNCATE vs VACUUM FULL Bill Moran
  • Re: question on TRUNCATE vs VACUUM FULL Mark Steben
  • PG writes a lot to the disk Laurent Raufaste
  • Re: What is the best way to storage music files in Postgresql Gregory Youngblood
  • Re: TB-sized databases Ron Mayer
  • Re: What is the best way to storage music files in Postgresql Craig Ringer
  • Re: question on TRUNCATE vs VACUUM FULL Chris
  • Re: What is the best way to storage music files in Postgresql Craig Ringer
  • Re: What is the best way to storage music files in Postgresql Gregory Stark
  • Re: Planner mis-estimation using nested loops followup KC ESL
• 18 March 2008
  • Re: What is the best way to storage music files in Postgresql david
  • Re: What is the best way to storage music files in Postgresql Craig Ringer
  • Re: What is the best way to storage music files in Postgresql Craig Ringer
  • Re: Planner mis-estimation using nested loops followup Stephen Denne
  • question on TRUNCATE vs VACUUM FULL Mark Steben
  • Re: What is the best way to storage music files in Postgresql Gregory Stark
  • Re: What is the best way to storage music files in Postgresql david
  • Re: Planner mis-estimation using nested loops followup Scott Marlowe
  • Re: What is the best way to storage music files in Postgresql david
  • Re: What is the best way to storage music files in Postgresql Andrej Ricnik-Bay
  • Re: TB-sized databases Ron Mayer
  • Re: Planner mis-estimation using nested loops followup Matthew
  • Re: Planner mis-estimation using nested loops followup Chris Kratz
  • Re: Planner mis-estimation using nested loops followup Joshua D. Drake
  • Planner mis-estimation using nested loops followup Chris Kratz
  • Re: Benchmark: Dell/Perc 6, 8 disk RAID 10 Michael Stone
  • Re: TB-sized databases Tom Lane
  • Re: What is the best way to storage music files in Postgresql Craig Ringer
  • Re: What is the best way to storage music files in Postgresql Andrej Ricnik-Bay
  • Re: Benchmark: Dell/Perc 6, 8 disk RAID 10 James Mansion
  • Re: TB-sized databases Ron Mayer
  • Re: What is the best way to storage music files in Postgresql Peter Koczan
  • Re: performance tools Franck Routier
  • Re: TB-sized databases Pablo Alcaraz
  • Re: TB-sized databases Bruce Momjian
  • Re: TB-sized databases Tom Lane
• 17 March 2008
  • Re: TB-sized databases Bruce Momjian

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