Re: planer picks a bad plan (seq-scan instead of index) - Mailing list pgsql-general

From Thomas H.
Subject Re: planer picks a bad plan (seq-scan instead of index)
Date
Msg-id 09b501c703d4$329eb380$0201a8c0@iwing
Whole thread Raw
In response to planer picks a bad plan (seq-scan instead of index) when adding an additional join  ("Thomas H." <me@alternize.com>)
List pgsql-general
> Have you run analyze on all the three tables since creating the
> database?

yes. even a forced ANALYZE FULL after the table loads: the tables were
TRUNCATE'd, refilled and ANALYZE FULL'ed some minutes before the tests.
there where no UPDATEs after the INSERTs...

- thomas



pgsql-general by date:

Previous
From: "Shoaib Mir"
Date:
Subject: Re: 8.1.2 postmaster died
Next
From: Alban Hertroys
Date:
Subject: Re: planer picks a bad plan (seq-scan instead of index)