On 21 Nov 2002, Peter T. Brown wrote:
> trouble is that this SQL is being automatically created by my
> object-relational mapping software and I can't easily customize it. Is
> there any other way I can force Postgres to do the most efficient thing?
Given no changes to the query, probably only by using blunt hammers like
seeing if set enable_seqscan=off or set enable_mergejoin=off helps, but
you'd want to wrap the statement with them (setting them globally is
bad) and you might not be able to do that as well if your software won't
let you.