Mailing lists [pgsql-performance]

14 February 2007

• 06:24   Re: cube operations slower than geo_distance() on production server Tom Lane
• 07:40   An unwanted seqscan Brian Herlihy
• 07:54   Re: An unwanted seqscan Tom Lane
• 08:19   Re: quad or dual core Intel CPUs Claus Guttesen
• 09:00   Benchmarking PGSQL? Krishna Kumar
• 09:17   Re: Benchmarking PGSQL? Shoaib Mir
• 12:58   Re: cube operations slower than geo_distance() on production server Merlin Moncure
• 14:35   Re: Benchmarking PGSQL? Luke Lonergan
• 15:21   Re: Benchmarking PGSQL? Merlin Moncure
• 15:28   reindex vs 'analyze' (was: Re: cube operations slower than geo_distance() on production server) Mark Stosberg
• 16:25   Re: quad or dual core Intel CPUs Kenji Morishige
• 17:07   Re: reindex vs 'analyze' (was: Re: cube operations slower than geo_distance() on production server) Tom Lane
• 17:13   Re: Proximity query with GIST and row estimation Guillaume Smet
• 17:24   Re: Benchmarking PGSQL? Luke Lonergan
• 17:43   Re: quad or dual core Intel CPUs Claus Guttesen
• 18:05   Re: reindex vs 'analyze' Mark Stosberg
• 18:12   Re: JOIN to a VIEW makes a real slow query Chuck D.
• 21:24   Re: How long should it take to insert 200,000 records? Lou O'Quin
• 21:32   Re: Proximity query with GIST and row estimation Paul Ramsey
• 22:40   Re: Benchmarking PGSQL? Josh Berkus