From: Peter Eisentraut <peter@eisentraut.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix for new Boolean node
Date: Mon, 17 Jan 2022 13:13:56 +0000
Message-ID: <E1n9Rpc-0002Be-E1@gemulon.postgresql.org> (raw)
Fix for new Boolean node
The token in nodeTokenType() is actually the whole rest of the string,
so we need to take into account the length to do the correct
comparison.
Without this, postgres_fdw tests fail under
-DWRITE_READ_PARSE_PLAN_TREES.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/cf925936ecc031355cd56fbd392ec3180517a110
Modified Files
--------------
src/backend/nodes/read.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: peter@eisentraut.org
Subject: Re: pgsql: Fix for new Boolean node
In-Reply-To: <E1n9Rpc-0002Be-E1@gemulon.postgresql.org>
References: <E1n9Rpc-0002Be-E1@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox