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 23:45:29 -0500
Message-ID: <4169.1045197929@sss.pgh.pa.us> (raw)
In-Reply-To: <877kc3jxsb.fsf@stark.dyndns.tv>
References: <20030213113156.T47380-100000@megazone23.bigpanda.com>
<87u1f7kf1y.fsf@stark.dyndns.tv>
<1915.1045178941@sss.pgh.pa.us>
<87isvnk708.fsf@stark.dyndns.tv>
<3081.1045187252@sss.pgh.pa.us>
<877kc3jxsb.fsf@stark.dyndns.tv>
Greg Stark <gsstark@mit.edu> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> Actually you are barking up the wrong tree entirely; I'm pretty certain
>> that truncate_useless_pathkeys *doesn't* remove this pathkey, because it
>> should notice that it is relevant to the mergejoin condition.
> No, truncate_useless_pathkeys actually returns NULL.
Mmm, you're right. It would accept the second pathkey if it got to
it --- but it doesn't, because the first pathkey (col1) isn't useful
for any merge condition.
Still, truncate_useless_pathkeys isn't the place to be dealing with this
issue. It's not in a position to generate multiple interpretations of
the same path, which is what we are really after here.
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: <4169.1045197929@sss.pgh.pa.us>
References: <20030213113156.T47380-100000@megazone23.bigpanda.com> <87u1f7kf1y.fsf@stark.dyndns.tv> <1915.1045178941@sss.pgh.pa.us> <87isvnk708.fsf@stark.dyndns.tv> <3081.1045187252@sss.pgh.pa.us> <877kc3jxsb.fsf@stark.dyndns.tv> <4169.1045197929@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