Andrew Dunstan <andrew@xxxxxxxxxxxx> writes: > Have you tried a) either turning off geqo or setting geqo_threshold > fairly high b) setting join_collapse_limit fairly high (assuming all the > above join targets are tables and not views, setting it to something > like 25 should do the trick. You'd have to do both, I think, to get an exhaustive plan search. In any case, this query is going to result in full table scans of most of the tables, because there just aren't very many WHERE constraints; so expecting it to run instantaneously is a pipe dream. I'm not sure that there's a significantly better plan to be had. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
