pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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:43:32 -0500
Message-ID: <20030618154332.GA20906@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?
> 
> I did
> 
> bogus=# create table crate(areaid text, touched timestamp);
> CREATE TABLE
> bogus=# create index crate_touched on crate(areaid, touched);
> CREATE INDEX
> 
> and then explained your query:
> 
>  GroupAggregate  (cost=64.14..66.48 rows=67 width=40)
>    ->  Sort  (cost=64.14..64.64 rows=200 width=40)
>          Sort Key: (touched >= (('now'::text)::timestamp(6) without time zone + '-2 years'::interval))
>          ->  Subquery Scan current  (cost=0.00..56.50 rows=200 width=40)
>                Filter: (touched >= (('now'::text)::timestamp(6) without time zone + '-10 years'::interval))
>                ->  Unique  (cost=0.00..54.50 rows=200 width=40)
>                      ->  Index Scan Backward using crate_touched on crate  (cost=0.00..52.00 rows=1000 width=40)
> 
> which looks perfectly reasonable.  Obviously, with no data or statistics
> the estimates are not to be trusted, but it sure looks to me like CVS
> tip should still be able to generate the right plan.  Did you do a full
> 'make clean' and rebuild when you updated?

I did a make distclean. I didn't do an initdb as I was able to restart
the database without a problem. I also tried a simpler query just doing
the distinct on without a where clause and the backwards index scan still
wasn't used.

I will try an initdb and then if that doesn't change things I will fetch
a new copy of the code from CVS, do another initdb and see what happens.



view thread (6+ messages)  latest in thread

Message-ID: <20030618154332.GA20906@wolff.to>
Permalink:  ../20030618154332.GA20906@wolff.to/
Also on:    postgresql.org/message-id/20030618154332.GA20906@wolff.to

 · 

reply

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: <20030618154332.GA20906@wolff.to>
  References: <20030618150210.GA20603@wolff.to> <21750.1055949519@sss.pgh.pa.us> <20030618154332.GA20906@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