From: Tom Lane <tgl@sss.pgh.pa.us>
To: Neil Conway <neilc@samurai.com>
Cc: Marc G. Fournier <scrappy@postgresql.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: *very* slow query to summarize data for a month ...
Date: Mon, 10 Nov 2003 18:42:09 -0500
Message-ID: <16200.1068507729@sss.pgh.pa.us> (raw)
In-Reply-To: <87ptfzx1b6.fsf@mailbox.samurai.com>
References: <20031110160144.C727@ganymede.hub.org>
<87ptfzx1b6.fsf@mailbox.samurai.com>
Neil Conway <neilc@samurai.com> writes:
> Interesting that we get the row count estimate for this index scan so
> wrong -- I believe this is the root of the problem. Hmmm... I would
> guess that the optimizer stats we have for estimating the selectivity
> of a functional index is pretty primitive, but I haven't looked into
> it at all. Tom might be able to shed some light...
Try "none at all". I have speculated in the past that it would be worth
gathering statistics about the contents of functional indexes, but it's
still on the to-do-someday list.
>> -> Seq Scan on traffic_logs ts (cost=0.00..38340.72 rows=8213 width=16) (actual time=5.02..-645982.04 rows=462198 loops=1)
> Uh, what?
That is bizarre, all right. Is it reproducible?
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, neilc@samurai.com, scrappy@postgresql.org
Subject: Re: *very* slow query to summarize data for a month ...
In-Reply-To: <16200.1068507729@sss.pgh.pa.us>
* 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