| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | dean deloach <deanelliotdeloach(at)hotmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #12749: WARNING: unrecognized node type: 701 |
| Date: | 2015-02-10 08:31:52 |
| Message-ID: | 54D9C1F8.90204@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 10/02/15 16:54, dean deloach wrote:
> 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
>
That is pretty scary - I'd still recommend raising it with Pivotal -
logging options changing the results of queries is ...*unexpected*...to
put it mildly!
Cheers
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | david.pozsar | 2015-02-10 09:56:58 | BUG #12754: The 'OF' template pattern of to_char() print incorrect results with negative offsets with minutes |
| Previous Message | dean deloach | 2015-02-10 03:54:02 | Re: BUG #12749: WARNING: unrecognized node type: 701 |