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-31 15:37:50 |
Message-ID: | 956da6e246ccfe5cd6305b5be9b6497c.squirrel@webmail.xs4all.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, August 26, 2014 14:24, Andrew Gierth wrote:
>>>>>> "Erik" == Erik Rijkers <er(at)xs4all(dot)nl> writes:
>
> >> They apply cleanly for me at 2bde297 whether with git apply or
> >> patch, except for the contrib one (which you don't need unless you
> >> want to run the contrib regression tests without applying the
> >> gsp-u patch).
>
> Erik> Ah, I had not realised that. Excluding that contrib-patch and
> Erik> only applying these three:
>
> Erik> gsp1.patch
> Erik> gsp2.patch
> Erik> gsp-doc.patch
>
> Erik> does indeed work (applies, compiles).
>
> I put up a rebased contrib patch anyway (linked off the CF).
>
> Did the "unrecognized node type" error go away, or do we still need to
> look into that?
>
I have found that the "unrecognized node type" error is caused by:
shared_preload_libraries = pg_stat_statements
in postgresql.conf (as my default compile script was doing).
If I disable that line the error goes away.
I don't know exactly what that means for the groping sets patches but I thought I'd mention it here.
Otherwise I've not run into any problems with GROUPING SETS.
Erik Rijkers
From | Date | Subject | |
---|---|---|---|
Next Message | Atri Sharma | 2014-08-31 15:39:59 | Re: Final Patch for GROUPING SETS - unrecognized node type: 347 |
Previous Message | Fabrízio de Royes Mello | 2014-08-31 15:34:54 | Re: Tips/advice for implementing integrated RESTful HTTP API |