From: Guillaume Smet <guillaume.smet@gmail.com>
To: Alexander Staubo <alex@purefiction.net>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Estimation problem with a LIKE clause containing a /
Date: Wed, 7 Nov 2007 14:38:04 +0100
Message-ID: <1d4e0c10711070538mf773791ke5950849299b142c@mail.gmail.com> (raw)
In-Reply-To: <88daf38c0711070525r1e7d6daft56970045de0ec8f4@mail.gmail.com>
References: <1d4e0c10711070453q214f089cpd144cbb5193d3c4f@mail.gmail.com>
<88daf38c0711070525r1e7d6daft56970045de0ec8f4@mail.gmail.com>
Alexander,
On 11/7/07, Alexander Staubo <alex@purefiction.net> wrote:
> That's a difference of less than *three milliseconds* -- a difference
> probably way within the expected overhead of running "explain
> analyze". Furthermore, all three queries use the same basic plan: a
> sequential scan with a filter. At any rate you're microbenchmarking in
> a way that is not useful to real-world queries. In what way are these
> timings a problem?
If you read my previous email carefully, you'll see they aren't a
problem: the problem is the estimation, not the timing. This is a self
contained test case of a far more complex query which uses a bad plan
containing a nested loop due to the bad estimate.
> Now all "like 'prefix%'" queries should use the index.
Not when you retrieve 50% of this table of 22k rows but that's not my
problem anyway. A seqscan is perfectly fine in this case.
Thanks anyway.
--
Guillaume
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: guillaume.smet@gmail.com, alex@purefiction.net
Subject: Re: Estimation problem with a LIKE clause containing a /
In-Reply-To: <1d4e0c10711070538mf773791ke5950849299b142c@mail.gmail.com>
* 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