Re: DISTINCT MAX() results mismatch on 8.2 and 8.3
От | Kevin Grittner |
---|---|
Тема | Re: DISTINCT MAX() results mismatch on 8.2 and 8.3 |
Дата | |
Msg-id | 480DC384.EE98.0025.0@wicourts.gov обсуждение исходный текст |
Ответ на | DISTINCT MAX() results mismatch on 8.2 and 8.3 (Taiki Yamaguchi <yamaguchi@sraoss.co.jp>) |
Ответы |
Re: DISTINCT MAX() results mismatch on 8.2 and 8.3
|
Список | pgsql-bugs |
>>> On Wed, Mar 26, 2008 at 9:23 PM, in message <20080327112308.b1e9a692.yamaguchi@sraoss.co.jp>, Taiki Yamaguchi <yamaguchi@sraoss.co.jp> 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 table "t1" CREATE TABLE > yamaguti=# insert into t1 select g, g from generate_series(1, 100) as g; > INSERT 0 100 > yamaguti=# select distinct max(i) from t1; > max > ----- > 100 > (1 row) > > 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). -Kevin
В списке pgsql-bugs по дате отправления: