On Tue, Jun 8, 2010 at 8:58 PM, Mark Rostron <mrost...@ql2.com> wrote: > I am looking for some specific information regarding optimizer behavior. > > We recently experienced a situation where a query that was previously using > a btree lookup (efficient) SWITCHED to using seqscan/hash lookup.
OK, before we go any further, got any explain analyze output of the fast and slow queries? -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
