I guess not. I usually vacuum with the analyze option box checked; I must have missed that this cycle.
It looks much better now. Thanks! From: bricklen [mailto:brick...@gmail.com] Sent: Wednesday, July 17, 2013 4:12 PM To: Ellen Rothman Cc: pgsql-performance@postgresql.org<mailto:pgsql-performance@postgresql.org> Subject: Re: [PERFORM] Seq Scan vs Index on Identical Tables in Two Different Databases On Wed, Jul 17, 2013 at 12:50 PM, Ellen Rothman <eroth...@datalinedata.com<mailto:eroth...@datalinedata.com>> wrote: I have the same table definition in two different databases on the same computer. When I explain a simple query in both of them, one database uses a sequence scan and the other uses an index scan. If I try to run the Seq Scan version without the where clause restricting the value of uniqueid, it uses all of the memory on my computer and never completes. How can I get the Seq Scan version to use an index scan? Did you run "ANALYZE your-table-name" before trying the sequential scan query? ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2013.0.3349 / Virus Database: 3204/6483 - Release Date: 07/11/13
