On Wednesday, May 22, 2013 10:03 PM fburgess wrote: > I did perform a explain analyze on the query.
Explain analyze doesn't help to collect statistics. You should use Analyze <table_name>. Ideally optimizer should have slected the best plan, but just to check you can once try with SET enable_hashjoin=off; And see what is the plan it chooses and does it pick up index scan on larger table? Could you please output of \d SARS_ACTS and \d SARS_ACTS_RUN? With Regards, Amit Kapila. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
