Skip site navigation (1) Skip section navigation (2)

Re: DISTINCT MAX() results mismatch on 8.2 and 8.3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org, "Taiki Yamaguchi" <yamaguchi(at)sraoss(dot)co(dot)jp>
Subject: Re: DISTINCT MAX() results mismatch on 8.2 and 8.3
Date: 2008-04-22 16:09:35
Message-ID: 22416.1208880575@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> yamaguti=# select distinct max(j) from t1;
>> ERROR:  could not find pathkey item to sort
 
> For the benefit of anyone searching the archives for the problem we
> just hit, this message also occurs in 8.3.1 and also occurs against
> the above test table for this statement:
 
> test=# select max(j) as "maxj" from t1 order by "maxj";
> ERROR:  could not find pathkey item to sort
 
> Neither statement causes the error when run against a build from
> REL8_3_STABLE from 35 minutes ago (2008-04-22 10:15 CDT).

Yeah, this was repaired here:
http://archives.postgresql.org/pgsql-committers/2008-03/msg00563.php

The fix will be in 8.3.2.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Eugen.KonkovDate: 2008-04-22 16:59:16
Subject: Re: BUG #4122: ./postres 'restart' does not start server with same options as 'start' does
Previous:From: Kris JurkaDate: 2008-04-22 15:53:19
Subject: Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group