On Fri, Oct 3, 2014 at 6:38 PM, Andrey Lizenko <lizenko79@xxxxxxxxx> wrote: > Is it possible to force optimizer choose the second plan without doing "set > enable_hashjoin = off;" ? > > Increasing of 'effective_cache_size' leads to similar thing with mergejoin, > other options (work_mem, shared_buffers. etc) do not change anything. Have you tried changing random_page_cost? In small databases where most of the data is cached anyway, lowering random_page_cost to somewhere between 1 and 2 usually leads to better planner decisions. Regards, Marti -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
