"Kevin Grittner" <[EMAIL PROTECTED]> 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 ta
>>> On Wed, Mar 26, 2008 at 9:23 PM, in message
<[EMAIL PROTECTED]>, Taiki Yamaguchi
<[EMAIL PROTECTED]> wrote:
> 8.3.0
> ==
> yamaguti=# create table t1 (i int, j int primary key);
> NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
> "t1_pkey" for tabl
Taiki Yamaguchi <[EMAIL PROTECTED]> writes:
> yamaguti=# select distinct max(j) from t1;
> ERROR: could not find pathkey item to sort
Fixed in HEAD and 8.3. Thanks for the report!
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
Taiki Yamaguchi <[EMAIL PROTECTED]> writes:
> If a column has a primary-key constraint, DISTINCT MAX() fails on 8.3.
> I know that the DISTINCT in this query has no meanings, but I wasn't
> certain that this was an intended behaviour or not (a bug). If it was a
> bug, would it be fixed in the futu
Hi,
I tried DISTINCT MAX() on the 8.2 and 8.3 as below.
8.2.6
==
yamaguti=# create table t1 (i int, j int primary key);
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"t1_pkey" for table "t1" CREATE TABLE
yamaguti=# insert into t1 select g, g from gen
