Turns out=2C and engineer at Pivotal=2C Shawn Yan=2C sent out an email to o=
ur team=2C acknowledging that is a known bug with GP=2C when connecting via=
ODBC/JDBC=2C and that the workaround is in fact=2C to change the log_state=
ment setting to either 'all' or 'none'
Dean=20
> Date: Tue=2C 10 Feb 2015 21:31:52 +1300
> From: mark.kirkwood@catalyst.net.nz
> To: deanelliotdeloach@hotmail.com=3B michael.paquier@gmail.com
> CC: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #12749: WARNING: unrecognized node type: 701
>=20
> On 10/02/15 16:54=2C dean deloach wrote:
> > Thanks for the response guys=2C really appreciate it. Turns out=2C it =
has
> > something to do with the log_statement config parameter on the DB. The
> > DBA changed and no one knew...these are the results we get when we
> > attempt to pull data from the GP instance via Datadirect drivers=2C for
> > different log_statement config values:
> >
> >
> > log_statement=3Dall - returns n records=2C no errors logged in Greenpl=
um
> > log file
> >
> > log_statement=3Dnone - returns n records=2C no errors logged in Greenp=
lum
> > log file
> >
> > log_statement=3Dmod - returns n-1 records=2C "unknown node: 701" error
> > logged in Greenplum log file
> >
> > log_statement=3Dddl - returns n-1 records=2C "unknown node: 701" error
> > logged in Greenplum log file
> >
>=20
> That is pretty scary - I'd still recommend raising it with Pivotal -=20
> logging options changing the results of queries is ...*unexpected*...to=20
> put it mildly!
>=20
> Cheers
>=20
> Mark
>=20
=