Re: Two different execution plan for the same request

From: Yeb Havinga <yebhavinga(at)gmail(dot)com>
To: "JOUANIN Nicolas (44)" <nicolas(dot)jouanin(at)dgfip(dot)finances(dot)gouv(dot)fr>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Two different execution plan for the same request
Date: 2010-07-07 08:59:23
Message-ID: 4C3441EB.8010405@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

JOUANIN Nicolas (44) wrote:
>
> The strange thing is that this morning explain analyze now gives a
> much better duration :
>
> There were no modification made on the database except a restart
> yesterday evening and a vacuumdb --analyse ran at night.
If the earlier bad query was run on a fresh imported database that was
not ANALYZEd, it would explain the different and likely bad plan. If you
want to know for sure this is the cause, instead of e.g. faulty
hardware, you could verify redoing the import + query without analyze.

regards,
Yeb Havinga

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Guillaume Smet 2010-07-07 08:59:56 Re: Two different execution plan for the same request
Previous Message Mark Kirkwood 2010-07-07 08:58:35 Re: [Slony1-general] WAL partition overloaded--by autovacuum?