• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Contributors
• 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
• Featured Users
• International Sites
• Propaganda
• Resources
• Weekly News
• Community login
  • Profile
  • Lost password

pgsql-performance 2007-02 Thread Index (2/2)

• Main Index
• [Prev Page]
• [Next Page]

• Re: Benchmarking PGSQL?, (continued)
  • Re: Benchmarking PGSQL? Merlin Moncure
  • Re: Benchmarking PGSQL? Luke Lonergan
  • Re: Benchmarking PGSQL? Merlin Moncure
  • Re: Benchmarking PGSQL? Josh Berkus
  • Re: Benchmarking PGSQL? Krishna Kumar
• An unwanted seqscan Brian Herlihy
• Re: An unwanted seqscan Tom Lane
• <Possible follow-ups>
• Re: An unwanted seqscan Brian Herlihy
• quad or dual core Intel CPUs Kenji Morishige
• Re: quad or dual core Intel CPUs Arjen van der Meijden
• Re: quad or dual core Intel CPUs Dan Harris
• Re: quad or dual core Intel CPUs Guillaume Smet
• Re: quad or dual core Intel CPUs Heikki Linnakangas
• Re: quad or dual core Intel CPUs Mark Kirkwood
• Re: quad or dual core Intel CPUs Claus Guttesen
• Re: quad or dual core Intel CPUs Kenji Morishige
• Re: quad or dual core Intel CPUs Claus Guttesen
• JOIN to a VIEW makes a real slow query Chuck D.
• Re: JOIN to a VIEW makes a real slow query Merlin Moncure
• Re: JOIN to a VIEW makes a real slow query Chuck D.
• Re: JOIN to a VIEW makes a real slow query Tom Lane
• Re: JOIN to a VIEW makes a real slow query Chuck D.
• CPU Usage Campbell, Lance
• Re: CPU Usage Alan Hodgson
• Proximity query with GIST and row estimation Guillaume Smet
• Re: Proximity query with GIST and row estimation Paul Ramsey
• Re: Proximity query with GIST and row estimation Guillaume Smet
• Re: Proximity query with GIST and row estimation Guillaume Smet
• Re: Proximity query with GIST and row estimation Guillaume Smet
• Question about Bitmap Heap Scan/BitmapAnd Guillaume Smet
• Re: Question about Bitmap Heap Scan/BitmapAnd Tom Lane
• Re: Question about Bitmap Heap Scan/BitmapAnd Guillaume Smet
• Re: Question about Bitmap Heap Scan/BitmapAnd Tom Lane
• Re: Question about Bitmap Heap Scan/BitmapAnd Guillaume Smet
• Re: Question about Bitmap Heap Scan/BitmapAnd Alvaro Herrera
• Re: Question about Bitmap Heap Scan/BitmapAnd Tom Lane
• Re: Question about Bitmap Heap Scan/BitmapAnd Guillaume Smet
• Re: Question about Bitmap Heap Scan/BitmapAnd Guillaume Smet
• many instances or many databases or many users? ismo . tuononen
• Re: many instances or many databases or many users? Heikki Linnakangas
• limit + order by is slow if no rows in result set Brian Cox
• Re: limit + order by is slow if no rows in result set Heikki Linnakangas
• <Possible follow-ups>
• Re: limit + order by is slow if no rows in result set Brian Cox
• Re: limit + order by is slow if no rows in result set Tom Lane
• Is there an equivalent for Oracle's user_tables.num_rows Virag Saksena
• Re: Is there an equivalent for Oracle's user_tables.num_rows Tom Lane
• Re: Is there an equivalent for Oracle's user_tables.num_rows Virag Saksena
• Re: Is there an equivalent for Oracle'suser_tables.num_rows Simon Riggs
• Re: Can anyone make this code tighter? Too slow, Please help! Mark Stosberg
• cube operations slower than geo_distance() on production server Mark Stosberg
• Re: cube operations slower than geo_distance() on production server Merlin Moncure
• Re: cube operations slower than geo_distance() on production server Mark Stosberg
• Re: cube operations slower than geo_distance() on production server Merlin Moncure
• Re: cube operations slower than geo_distance() on production server Merlin Moncure
• Re: cube operations slower than geo_distance() on production server Mark Stosberg
• Re: cube operations slower than geo_distance() on production server Merlin Moncure
• Re: cube operations slower than geo_distance() on production server Merlin Moncure
• Re: cube operations slower than geo_distance() on production server Mark Stosberg
• Re: cube operations slower than geo_distance() on production server Tom Lane
• Re: cube operations slower than geo_distance() on production server Merlin Moncure
• reindex vs 'analyze' (was: Re: cube operations slower than geo_distance() on production server) Mark Stosberg
• Re: reindex vs 'analyze' (was: Re: cube operations slower than geo_distance() on production server) Tom Lane
• Re: reindex vs 'analyze' Mark Stosberg
• Re: reindex vs 'analyze' Mark Stosberg
• Recreate big table Gábriel Ákos
• Re: Recreate big table Daniel Cristian Cruz
• Disk saturation Carlos H. Reimer
• Re: Speed up this query Mark Stosberg
• stats collector process high CPU utilization Benjamin Minshall
• Re: stats collector process high CPU utilization Tom Lane
• Re: stats collector process high CPU utilization Benjamin Minshall
• Re: stats collector process high CPU utilization Tom Lane
• Re: stats collector process high CPU utilization Benjamin Minshall
• Re: stats collector process high CPU utilization Tom Lane
• Re: stats collector process high CPU utilization Benjamin Minshall
• Re: stats collector process high CPU utilization Tom Lane
• Re: stats collector process high CPU utilization Benjamin Minshall
• Re: stats collector process high CPU utilization Tom Lane
• Re: stats collector process high CPU utilization minshall
• Re: stats collector process high CPU utilization Tom Lane
• Re: stats collector process high CPU utilization Alvaro Herrera
• Re: stats collector process high CPU utilization Tom Lane
• Re: stats collector process high CPU utilization Tom Lane
• Re: stats collector process high CPU utilization Benjamin Minshall
• Re: stats collector process high CPU utilization Tom Lane
• Re: stats collector process high CPU utilization Benjamin Minshall
• Help Needed Muruganantham M
• Re: Help Needed Richard Huxton
• Re: explain analyze output for review (was: optimizing a geo_distance()...) Hiltibidal, Robert
• <Possible follow-ups>
• Re: explain analyze output for review (was: optimizing a geo_distance()...) Hiltibidal, Robert
• How long should it take to insert 200,000 records? Karen Hill
• Re: How long should it take to insert 200,000 records? Tom Lane
• Re: How long should it take to insert 200,000 records? Karen Hill
• Re: How long should it take to insert 200,000 records? Mark Kirkwood
• Re: How long should it take to insert 200,000 records? Tom Lane
• Re: How long should it take to insert 200,000 records? Lou O'Quin
• Re: How long should it take to insert 200,000 records? Csaba Nagy
• Re: How long should it take to insert 200,000 records? Scott Marlowe
• Re: How long should it take to insert 200,000 records? Merlin Moncure
• Re: How long should it take to insert 200,000 records? Scott Marlowe
• Re: How long should it take to insert 200,000 records? Merlin Moncure
• Re: How long should it take to insert 200,000 records? Mark Lewis
• Re: How long should it take to insert 200,000 records? Bruno Wolff III
• Re: How long should it take to insert 200,000 records? Merlin Moncure
• Re: How long should it take to insert 200,000 records? Mark Lewis
• <Possible follow-ups>
• Re: How long should it take to insert 200,000 records? Hiltibidal, Robert
• optimizing a geo_distance() proximity query Mark Stosberg
• Re: optimizing a geo_distance() proximity query Oleg Bartunov
• Re: optimizing a geo_distance() proximity query Bruno Wolff III
• Re: optimizing a geo_distance() proximity query Mark Stosberg
• Re: optimizing a geo_distance() proximity query Merlin Moncure
• Re: optimizing a geo_distance() proximity query (example and benchmark) Mark Stosberg
• Re: optimizing a geo_distance() proximity query (example and benchmark) Bruno Wolff III
• Re: explain analyze output for review (was: optimizing a geo_distance()...) Mark Stosberg
• Re: explain analyze output for review (was: optimizing a geo_distance()...) Adam Rich
• Re: explain analyze output: vacuuming made a big difference. Mark Stosberg
• Re: explain analyze output for review (was: optimizing a geo_distance()...) Bruno Wolff III
• Re: optimizing a geo_distance() proximity query (example and benchmark) Merlin Moncure
• tip: faster sorting for proximity queries by using cube_distance() Mark Stosberg
• Re: optimizing a geo_distance() proximity query Bruno Wolff III
• OT: Mac OS X disk buffer cache Kevin Murphy
• trouble with a join on OS X Kirk Wythers
• Re: trouble with a join on OS X Steinar H. Gunderson
• Re: trouble with a join on OS X Kirk Wythers
• Re: trouble with a join on OS X Richard Huxton
• Re: trouble with a join on OS X Gábriel Ákos
• Re: trouble with a join on OS X Tom Lane
• Re: trouble with a join on OS X Kirk Wythers
• Re: trouble with a join on OS X Steinar H. Gunderson
• Re: trouble with a join on OS X Tom Lane
• Re: trouble with a join on OS X Kirk Wythers
• Re: trouble with a join on OS X Tom Lane
• Re: trouble with a join on OS X Kirk Wythers
• Re: trouble with a join on OS X Tom Lane
• Re: trouble with a join on OS X Luke Lonergan
• Re: trouble with a join on OS X Joshua D. Drake
• Re: trouble with a join on OS X Luke Lonergan
• Re: trouble with a join on OS X Kirk Wythers
• Re: trouble with a join on OS X Joshua D. Drake
• Re: trouble with a join on OS X Geoffrey
• Re: trouble with a join on OS X Joshua D. Drake
• Re: trouble with a join on OS X Kirk Wythers
• Re: trouble with a join on OS X Tom Lane
• Re: trouble with a join on OS X Kirk Wythers
• Re: trouble with a join on OS X Joshua D. Drake
• Re: trouble with a join on OS X Tom Lane
• Re: trouble with a join on OS X Shane Ambler
• Re: trouble with a join on OS X Kirk Wythers
• Re: trouble with a join on OS X Shane Ambler
• <Possible follow-ups>
• Re: trouble with a join on OS X Kirk Wythers
• index scan through a subquery Bill Howe
• Re: index scan through a subquery Tom Lane
• Re: index scan through a subquery Bill Howe
• drive configuration for a new server Ben
• Re: drive configuration for a new server Jeff Frost
• Re: drive configuration for a new server Ben
• Re: int4 vs varchar to store ip addr Michael Artz
• Subselect query enhancement Michael Artz
• Re: Subselect query enhancement Richard Huxton
• Re: Subselect query enhancement Michael Artz
• Re: Subselect query enhancement Richard Huxton
• Re: Subselect query enhancement Michael Artz
• Re: Subselect query enhancement Richard Huxton
• Re: Subselect query enhancement Ted Allen
• Re: Subselect query enhancement Michael Artz
• Re: Subselect query enhancement Andrew Lazarus
• Re: Subselect query enhancement Frank Wiles
• Using statement_timeout as a performance tool? Mark Stosberg
• Re: Tuning Mischa Sandberg
• Re: Tuning Harald Armin Massa

---

• Main Index
• [Prev Page]
• [Next Page]

---

Mail converted by MHonArc