Search Postgresql Archives

Re: planer picks a bad plan (seq-scan instead of index)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "mike" <mike@xxxxxxxxxxxxxxxx>
Subject: Re: planer picks a bad plan (seq-scan instead of index)
From: "Thomas H." <me@xxxxxxxxxxxxx>
Date: Thu, 9 Nov 2006 08:53:50 +0100
Cc: <pgsql-general@xxxxxxxxxxxxxx>
References: <098a01c7039e$c820fe30$0201a8c0@iwing> <1163044647.6581.11.camel@xxxxxxxxxxxxxxxxxxxxx>

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 wereTRUNCATE'd, refilled and ANALYZE FULL'ed some minutes before the tests.there where no UPDATEs after the INSERTs...

- thomas

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- planer picks a bad plan (seq-scan instead of index) when adding an additional join
  - From: Thomas H.
- Re: planer picks a bad plan (seq-scan instead of index)
  - From: mike

Prev by Date: Re: 8.1.2 postmaster died
Next by Date: Re: planer picks a bad plan (seq-scan instead of index)
Previous by thread: Re: planer picks a bad plan (seq-scan instead of index)
Next by thread: Re: planer picks a bad plan (seq-scan instead of index)
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux