http://blog.charcoalphile.com/2009/01/22/postgresql-and-select-distinct-on-large-tables/ On Databases, Recovery, Tech Sat, 31 Jul 2010 08:24:31 +0000 http://wordpress.org/?v=2.2.1 http://blog.charcoalphile.com/2009/01/22/postgresql-and-select-distinct-on-large-tables/#comment-2485 admin Wed, 11 Feb 2009 16:48:12 +0000 http://blog.charcoalphile.com/2009/01/22/postgresql-and-select-distinct-on-large-tables/#comment-2485 Yeah, the problem was PostgreSQL's cost estimate was way off, so it never attempted an index scan. After forcing it to use an index, and running VACUUM ANALYZE, it started choosing an index scan over a seqscan. Yeah, the problem was PostgreSQL’s cost estimate was way off, so it never attempted an index scan. After forcing it to use an index, and running VACUUM ANALYZE, it started choosing an index scan over a seqscan.

]]> http://blog.charcoalphile.com/2009/01/22/postgresql-and-select-distinct-on-large-tables/#comment-2483 Ivan Pavlov Wed, 11 Feb 2009 11:33:53 +0000 http://blog.charcoalphile.com/2009/01/22/postgresql-and-select-distinct-on-large-tables/#comment-2483 Hmph. Have you run VACUUM ANALYZE on this table before comparing query plans? Hmph. Have you run VACUUM ANALYZE on this table before comparing query plans?

]]>