From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix write/read of empty string fields in Nodes.
Date: Mon, 26 Sep 2022 09:40:59 -0400
Message-ID: <3435227.1664199659@sss.pgh.pa.us> (raw)
In-Reply-To: <E1ocoEC-00269r-II@gemulon.postgresql.org>
References: <E1ocoEC-00269r-II@gemulon.postgresql.org>
Peter Eisentraut <peter@eisentraut.org> writes:
> Fix write/read of empty string fields in Nodes.
This really should've included a catversion bump, I think.
Maybe there are no cases where this affects a Node type
we can store today, but I'm unconvinced of that.
regards, tom lane
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: tgl@sss.pgh.pa.us, peter@eisentraut.org
Subject: Re: pgsql: Fix write/read of empty string fields in Nodes.
In-Reply-To: <3435227.1664199659@sss.pgh.pa.us>
References: <E1ocoEC-00269r-II@gemulon.postgresql.org> <3435227.1664199659@sss.pgh.pa.us>
* 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