From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Show values of SET statements as constants in pg_stat_statements
Date: Mon, 30 Sep 2024 01:16:47 -0400
Message-ID: <1364409.1727673407@sss.pgh.pa.us> (raw)
In-Reply-To: <E1sv8YF-001WMH-Ht@gemulon.postgresql.org>
References: <E1sv8YF-001WMH-Ht@gemulon.postgresql.org>
Michael Paquier <michael@paquier.xyz> writes:
> Show values of SET statements as constants in pg_stat_statements
Shouldn't this have included a catversion bump? The parsenodes.h
change would for example break new-style SQL functions that include
a SET command. Probably a narrow use-case, but still.
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 using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Show values of SET statements as constants in pg_stat_statements
In-Reply-To: <1364409.1727673407@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