Thanks for the response guys, really appreciate it. Turns out, 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, for different log_statement config values:
log_statement=all - returns n records, no errors logged in Greenplum log file log_statement=none - returns n records, no errors logged in Greenplum log file log_statement=mod - returns n-1 records, "unknown node: 701" error logged in Greenplum log file log_statement=ddl - returns n-1 records, "unknown node: 701" error logged in Greenplum log file Dean
> Date: Tue, 10 Feb 2015 11:03:04 +0900
> Subject: Re: [BUGS] BUG #12749: WARNING: unrecognized node type: 701
> From: michael(dot)paquier(at)gmail(dot)com
> To: mark(dot)kirkwood(at)catalyst(dot)net(dot)nz
> CC: deanelliotdeloach(at)hotmail(dot)com; pgsql-bugs(at)postgresql(dot)org
>
> On Tue, Feb 10, 2015 at 10:53 AM, Mark Kirkwood wrote:
> > On 09/02/15 13:04, deanelliotdeloach(at)hotmail(dot)com wrote:
> >> Loading DB version:
> >> PostgreSQL 8.2.15 (Greenplum Database 4.2.6.3 build 2)
> >
> > It is probably best to raise this with Greenplum (Pivotal these days).
>
> Yup, there is nothing we can really do, and 8.2 is out of community
> support since the end of 2011.
> --
> Michael