From: Bruno Wolff III <bruno@wolff.to>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Recent 7.4 change slowed down a query by a factor of 3
Date: Wed, 18 Jun 2003 10:53:40 -0500
Message-ID: <20030618155340.GA21222@wolff.to> (raw)
In-Reply-To: <21750.1055949519@sss.pgh.pa.us>
References: <20030618150210.GA20603@wolff.to>
<21750.1055949519@sss.pgh.pa.us>
On Wed, Jun 18, 2003 at 11:18:39 -0400,
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Bruno Wolff III <bruno@wolff.to> writes:
> > The query below was running in a bit under 300ms on a version of 7.4
> > from less than a week ago until I updated to the version from last night.
> > Now it takes about 800ms using a significantly different plan.
>
> Something fishy here. Will it use the right plan if you set
> enable_seqscan off?
After doing an initdb I got the expected plan.
This is a static db used for dynamic web pages and the script that loads
the db does a vacumm analyze at the end. So the db should have had the
information needed to pick the correct plan. Possibly something changed
that affected the information needed for planning, but the value used
to indicate an initdb was needed wasn't changed.
In the future if I see odd stuff I will try doing an initdb before reporting
a potential problem. Thanks for your help.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: bruno@wolff.to, tgl@sss.pgh.pa.us
Subject: Re: Recent 7.4 change slowed down a query by a factor of 3
In-Reply-To: <20030618155340.GA21222@wolff.to>
References: <20030618150210.GA20603@wolff.to> <21750.1055949519@sss.pgh.pa.us> <20030618155340.GA21222@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox