On Wed, Nov 23, 2011 at 7:24 PM, Gary Warner <g...@cis.uab.edu> wrote: > See that "Seq Scan on link_url"? We can't figure out why that is there! We > should be scanning for a matching "urlid" and we have an index on "urlid"? > > When this is happening in a "two table" version of this problem, we can get > temporary relief by giving the statement: > > set enable_seqscan = false;
Obviously, because it thinks the index scan will perform worse. It would be interesting to see the explain analyze with enable_seqscan=false to see why -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
