;m assuming the
planner chooses the plan with the lowest cost.
I'd much prefer it *does* the sequential scan of the empty table and
goes with the other parts of the plan.
Thanks,
Lucas Madar
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
3941949 width=490)
This seems like a much more sensible query plan. But it seems to think
doing a sequential scan on the *empty* item table is excessively
expensive in this case.
Aside from enable_seqscan=false, is there any way I can make the query
planner not balk over doing a seqscan on
