Re: Final Patch for GROUPING SETS - unrecognized node type: 347

From: "Erik Rijkers" <er(at)xs4all(dot)nl>
To: "Andrew Gierth" <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Atri Sharma" <atri(dot)jiit(at)gmail(dot)com>
Subject: Re: Final Patch for GROUPING SETS - unrecognized node type: 347
Date: 2014-08-26 08:25:18
Message-ID: d19e1a7a64a631edd9ce0cc0da9bbd20.squirrel@webmail.xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, August 25, 2014 07:21, Andrew Gierth wrote:
> Here is the new version of our grouping sets patch. This version
> supersedes the previous post.

The patches did not apply anymore so I applied at 73eba19aebe0. There they applied OK, and make && make check was OK.

drop table if exists items_sold;
create table items_sold as
select * from (
values
('Foo', 'L', 10)
, ('Foo', 'M', 20)
, ('Bar', 'M', 15)
, ('Bar', 'L', 5)
) as f(brand, size, sales) ;

select brand, size, grouping(brand, size), sum(sales) from items_sold group by rollup(brand, size);
--> WARNING: unrecognized node type: 347

I suppose that's not correct.

thanks,

Erik Rijkers

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2014-08-26 08:25:29 Re: postgresql latency & bgwriter not doing its job
Previous Message Andres Freund 2014-08-26 08:18:18 Re: postgresql latency & bgwriter not doing its job