Hi!
I suppose there is a bug in optimizer. When somehting like
SELECT min(id) from bla-bla;
is executed, it optimizer selects sequential scan even if any index on
"id" exists.
This is not a Good Thing, isn't it?
--
Best regards,
Nick Gazaloff
Hi!
When I execute
SELECT min(id) FROM test;
PostgreSQL optimizer uses sequential scan for performing the query
even if any index on "id" exists. VACUUM ANALYZE just before the query
doesn't help. Runtime option to not use sequenatial scans doesn't help.
So, I suppose it's a real bug.
--
Best
