From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: exclusion@gmail.com
Subject: BUG #18340: BitString may break nodetoString() conversion for a raw parse tree
Date: Tue, 13 Feb 2024 09:00:00 +0000
Message-ID: <18340-4aa1ae6ed4121912@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18340
Logged by: Alexander Lakhin
Email address: exclusion@gmail.com
PostgreSQL version: 16.2
Operating system: Ubuntu 22.04
Description:
When a server compiled with -DWRITE_READ_PARSE_PLAN_TREES, the following
query:
SELECT x' 0';
produces:
ERROR: did not find '}' at end of input node
Observed starting from commit 40ad8f9de, which implemented
WRITE_READ_PARSE_PLAN_TREES for raw parse trees.
More interesting results may be obtained (e.g.,
WARNING: outfuncs/readfuncs failed to produce an equal raw parse tree
), but with raw trees only, not with node trees stored in the database,
considering core code.
Still codesearch.debian.net shows that nodeToString() used by several
extensions: pg_qual_stats, pgpool2, hypopg, pglogical; perhaps some of
them use that conversion unsafely (without processing a node with
transformExpr() or so).
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 using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, exclusion@gmail.com
Subject: Re: BUG #18340: BitString may break nodetoString() conversion for a raw parse tree
In-Reply-To: <18340-4aa1ae6ed4121912@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