On Wed, Apr 27, 2011 at 3:04 AM, Merlin Moncure <mmoncure@xxxxxxxxx> wrote: > The very first thing to check is effective_cache_size and to set it to > a reasonable value. > The problem there, I think, is that the planner is doing a full join, instead of a semi-join. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
