Re: [sqlsmith] ERROR: badly formatted node string "RESTRICTINFO...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andreas Seltenreich <seltenreich(at)gmx(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [sqlsmith] ERROR: badly formatted node string "RESTRICTINFO...
Date: 2017-04-09 15:51:52
Message-ID: 11668.1491753112@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andreas Seltenreich <seltenreich(at)gmx(dot)de> writes:
> regression=> select (select max(result) from fdw_postgres.num_result) from tt0;
> ERROR: badly formatted node string "RESTRICTINFO :clause {NULLTEST :"...
> CONTEXT: parallel worker

Apparently, postgres_fdw is trying to store RestrictInfos in the
fdw_private field of a ForeignScan node. That won't do; those aren't
supposed to be present in a finished plan tree, so there's no readfuncs.c
support for them (and we're not adding it).

Don't know if this is a new bug, or ancient but not previously reachable.
It seems to be nearly the inverse of the problem you found yesterday,
in which postgres_fdw was stripping RestrictInfos sooner than it really
ought to. Apparently that whole business needs a fresh look.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2017-04-09 16:59:09 Re: [HACKERS] Small issue in online devel documentation build
Previous Message Aleksander Alekseev 2017-04-09 13:25:16 Re: [PATCH] Remove unused argument in btree_xlog_split