From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Stark <gsstark@mit.edu>
Cc: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
Cc: Ole Langbehn <ole@freiheit.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: sequential scan on select distinct
Date: Wed, 06 Oct 2004 15:38:26 -0400
Message-ID: <29194.1097091506@sss.pgh.pa.us> (raw)
In-Reply-To: <874ql7ztnb.fsf@stark.xeocode.com>
References: <200410061130.58625.ole@freiheit.com>
<opsff1mmp8cq72hf@musicbox>
<874ql7ztnb.fsf@stark.xeocode.com>
Greg Stark <gsstark@mit.edu> writes:
> why isn't a "skip index scan" plan available? Well, nobody's written the code
> yet.
I don't really think it would be a useful plan anyway. What *would* be
useful is to support HashAggregate as an implementation alternative for
DISTINCT --- currently I believe we only consider that for GROUP BY.
The DISTINCT planning code is fairly old and crufty and hasn't been
redesigned lately.
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, gsstark@mit.edu, lists@boutiquenumerique.com, ole@freiheit.com
Subject: Re: sequential scan on select distinct
In-Reply-To: <29194.1097091506@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