Date: Sun, 28 Aug 2005 03:42:40 +0200
From: Tobias Brox <tobias@nordicbet.com>
To: Mark Kirkwood <markir@paradise.net.nz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Tobias Brox <tobias@nordicbet.com>,
	pgsql-performance@postgresql.org
Subject: Re: Limit + group + join
Message-ID: <20050828014240.GB5736@tobias.lan>
References: <20050826002709.GK10328@tobias.lan>
	<430E85ED.60109@paradise.net.nz> <9501.1125071193@sss.pgh.pa.us>
	<430FD61A.3020902@paradise.net.nz> <10922.1125181071@sss.pgh.pa.us>
	<431109FB.6000505@paradise.net.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <431109FB.6000505@paradise.net.nz>
Organization: Group Nordicbet
User-Agent: Mutt/1.5.10i

[Tom Lane]
> I looked into this and (...) I've committed some changes that hopefully will
> let 8.1 be smarter about GROUP BY ... LIMIT queries.

[Mark Kirkwood]
> Very nice :-)
(...)
> This is 8.1devel from today.

Splendid :-) Unfortunately we will not be upgrading for some monthes still,
but anyway I'm happy.  This provides yet another good argument for upgrading
sooner.  I'm also happy to see such a perfect match:

 - A problem that can be reduced from beeing complex and
   production-specific, to simple and easily reproducible.
   
 - Enthusiastic people testing it and pinpointing even more precisely what
   conditions will cause the condition
   
 - Programmers actually fixing the issue
 
 - Testers verifying that it was fixed
 
Long live postgresql! :-) 

-- 
Notice of Confidentiality: This email is sent unencrypted over the network,
and may be stored on several email servers; it can be read by third parties
as easy as a postcard.  Do not rely on email for confidential information.