Re: Final Patch for GROUPING SETS - unrecognized node type: 347 - Mailing list pgsql-hackers

From Atri Sharma
Subject Re: Final Patch for GROUPING SETS - unrecognized node type: 347
Date
Msg-id CAOeZViczFdGyb4F9Eqig9cbhCDQfBa8cCJg5WuXiFRF2YmUAvg@mail.gmail.com
Whole thread Raw
In response to Re: Final Patch for GROUPING SETS - unrecognized node type: 347  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Final Patch for GROUPING SETS - unrecognized node type: 347
List pgsql-hackers


On Sunday, August 31, 2014, Andres Freund <andres@2ndquadrant.com> wrote:
On 2014-08-31 21:09:59 +0530, Atri Sharma wrote:
> On Sun, Aug 31, 2014 at 9:07 PM, Erik Rijkers <er@xs4all.nl> wrote:
> > I have found that the "unrecognized node type" error is caused by:

It's a warning, not an error, right?

> > 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  think thats more of a library linking problem rather than a problem with
> the patch. I couldnt reproduce it,though.

I think it's vastly more likely that the patch simply didn't add the new
expression types to pg_stat_statements.c:JumbleExpr().



Must have run the above diagnosis in a wrong manner then, I will check.Thanks for the heads up!

Regards,

Atri 


--
Regards,
 
Atri
l'apprenant

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: improving speed of make check-world
Next
From: Tom Lane
Date:
Subject: Re: Re: [BUGS] Re: BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns