From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Stark <gsstark@mit.edu>
Cc: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Cc: pgsql-general@postgresql.org
Subject: Re: index scan with index cond on first column doesn't recognize sort order of second column
Date: Thu, 13 Feb 2003 18:29:01 -0500
Message-ID: <1915.1045178941@sss.pgh.pa.us> (raw)
In-Reply-To: <87u1f7kf1y.fsf@stark.dyndns.tv>
References: <20030213113156.T47380-100000@megazone23.bigpanda.com>
<87u1f7kf1y.fsf@stark.dyndns.tv>
Greg Stark <gsstark@mit.edu> writes:
> I'm not clear on what truncate_useless_pathkeys is doing.
It's throwing away pathkey info that isn't relevant for the current
query (and would cause the planner to consider a multi-column-index
scan as better-ordered than a scan of an index with fewer columns,
when no such thing is true if the extra columns aren't relevant).
> If it were changed to just keep the suffix would that break other things?
Yes, that would be completely backwards.
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 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-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, gsstark@mit.edu, sszabo@megazone23.bigpanda.com
Subject: Re: index scan with index cond on first column doesn't recognize sort order of second column
In-Reply-To: <1915.1045178941@sss.pgh.pa.us>
References: <20030213113156.T47380-100000@megazone23.bigpanda.com> <87u1f7kf1y.fsf@stark.dyndns.tv> <1915.1045178941@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