Re: [PERFORM] Seq Scan vs Index on Identical Tables in Two Different Databases

2013-07-17 Thread Ellen Rothman
sql-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 mailto:eroth...@datalinedata.com>> wrote: I have the same table definition in two different databases on the same comp

Re: [PERFORM] Seq Scan vs Index on Identical Tables in Two Different Databases

2013-07-17 Thread David Kerr
On Wed, Jul 17, 2013 at 07:50:06PM +, Ellen Rothman 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 vers

Re: [PERFORM] Seq Scan vs Index on Identical Tables in Two Different Databases

2013-07-17 Thread bricklen
On Wed, Jul 17, 2013 at 12:50 PM, Ellen Rothman 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

[PERFORM] Seq Scan vs Index on Identical Tables in Two Different Databases

2013-07-17 Thread Ellen Rothman
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, i