Jann Röder wrote:
Am 23.08.10 12:18, schrieb Scott Marlowe:
>> What happens if you try
>>
>> set enable_seqscan=off;
>> (your query here)
>>
> Tried that already. The query plan is exactly the same.
Exactly? Not even the cost shown for the seq scan changed?
You are almost certainly omitting some crucial piece of information
in your report. Please look over this page and post a more complete
report. In particular, please show the results of \d for both tables
(or of pg_dump -s -t 'tablename'), your complete postgresql.conf file
stripped of comments, and a description of your hardware and OS.
-Kevin
