Message-ID: <4E021FF7.7@2ndQuadrant.com>
Date: Wed, 22 Jun 2011 13:01:43 -0400
From: Greg Smith <greg@2ndQuadrant.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.1.16) Gecko/20110505 Icedove/3.0.11
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: seq scan in the case of max() on the primary key column
References: <BANLkTikntdSrhneCPzPutY9T-sAQpFXTMw@mail.gmail.com>
	<BANLkTikuFEyOse=sUoH0BXYrpUW=7Pp_tw@mail.gmail.com>
	<4DFA4D2F.8020101@peak6.com>
	<BANLkTim5saGCxhLCAx4nEUQ4tZuOSy65fg@mail.gmail.com>
In-Reply-To: <BANLkTim5saGCxhLCAx4nEUQ4tZuOSy65fg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 06/22/2011 05:55 AM, Marti Raudsepp wrote:
> Now I created a wiki snippet page for this handy
> feature here:
> https://wiki.postgresql.org/wiki/Efficient_min/max_over_partitioned_table
>    

I just tweaked this a bit to document the version compatibility issues 
around it and make it easier to follow.  I think that's now the page we 
should point people toward when this pops up again.  Between that and my 
blog post I reference in it, they can find all the details and a 
workaround in one place.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books