Re: BUG #7703: Error with partitioning with distinct over aggregate - Mailing list pgsql-bugs

From Maxim Boguk
Subject Re: BUG #7703: Error with partitioning with distinct over aggregate
Date
Msg-id CAK-MWwTFL==S7SdL4S0PtXqfkaihoZf8PPrGBwWcSczdJRd-MQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #7703: Error with partitioning with distinct over aggregate  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Nov 27, 2012 at 5:01 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> maxim.boguk@gmail.com writes:
>> test=# create table test (id serial);
>> NOTICE:  CREATE TABLE will create implicit sequence "test_id_seq" for serial
>> column "test.id"
>> CREATE TABLE
>> test=# create index test_id_key on test(id);
>> CREATE INDEX
>> test=# create table test_part_1 (like test including all) INHERITS (test);
>> NOTICE:  merging column "id" with inherited definition
>> CREATE TABLE
>> test=# explain analyze select distinct min(id) from test;
>> ERROR:  failed to re-find MinMaxAggInfo record
>
> Fixed, thanks for the report.
>
>                         regards, tom lane

Thank you very much.

PS: I know that the query sounds stupid, but most CMS/ORM
unfortunately could produce unlimited amount of strange/stupid
queries.

--
Maxim Boguk
Senior Postgresql DBA
http://www.postgresql-consulting.ru/

pgsql-bugs by date:

Previous
From: Peter Kroon
Date:
Subject: Re: npgssql 5gb installation
Next
From: tgarnett@panjiva.com
Date:
Subject: BUG #7709: psql \copy csv terminates with \. in quoted region