From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andreas Seltenreich <seltenreich@gmx.de>
cc: pgsql-hackers@postgresql.org
Subject: Re: [sqlsmith] ERROR: badly formatted node string "RESTRICTINFO...
In-reply-to: <87tw5x4vcu.fsf@credativ.de>
References: <87tw5x4vcu.fsf@credativ.de>
Comments: In-reply-to Andreas Seltenreich <seltenreich@gmx.de>
	message dated "Sun, 09 Apr 2017 14:29:53 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11667.1491753112.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 09 Apr 2017 11:51:52 -0400
Message-ID: <11668.1491753112@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Andreas Seltenreich <seltenreich@gmx.de> writes:
> regression=3D> select (select max(result) from fdw_postgres.num_result) f=
rom 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


--=20
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers