Re: possible de-optimization of multi-column index plans in 8.3 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: possible de-optimization of multi-column index plans in 8.3
Date
Msg-id 15878.1173746650@sss.pgh.pa.us
Whole thread Raw
In response to possible de-optimization of multi-column index plans in 8.3  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> One of the Sun benchmarking guys ran across this issue, using a fairly 
> recent (within the last 4 weeks) 8.3 snapshot.  It appears to me that the 
> 8.3 planner is unable to tell that, if the value for the first column of 
> an index scan is a constant, the second column doesn't need to be sorted.  

Works for me.  Care to provide a self-contained test case?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values
Next
From: Gregory Stark
Date:
Subject: Re: My honours project - databases using dynamically attached entity-properties