Re: MAX() and multi-column index on a partitioned table? - Mailing list pgsql-performance

From Dave Johansen
Subject Re: MAX() and multi-column index on a partitioned table?
Date
Msg-id CAAcYxUeoVw3CPFkvoCA7cETzNb-rBRpBeb4n3Dw3U6az6Zj-0g@mail.gmail.com
Whole thread Raw
In response to Re: MAX() and multi-column index on a partitioned table?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: MAX() and multi-column index on a partitioned table?
List pgsql-performance
On Fri, May 22, 2015 at 3:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Dave Johansen <davejohansen@gmail.com> writes:
> I'm trying to call MAX() on the first value of a multi-column index of a
> partitioned table and the planner is choosing to do a sequential scan
> instead of an index scan. Is there something I can do to fix this?

What PG version are you using?  9.1 or newer should know how to do this
with a merge append of several indexscans.

Sorry, I should have mentioned that in the original email. I'm using 8.4.20 on RHEL 6. From your reply, it sounds like this is the expected behavior for 8.4 and 9.0. Is that the case?
Thanks,
Dave

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: MAX() and multi-column index on a partitioned table?
Next
From: Tom Lane
Date:
Subject: Re: MAX() and multi-column index on a partitioned table?