From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: leiyanliang@highgo.com <leiyanliang@highgo.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17077: about three parameters in postgresql 13.3
Date: Sat, 17 Jul 2021 13:24:08 -0400
Message-ID: <202107171724.hycens5f43ho@alvherre.pgsql> (raw)
In-Reply-To: <66575.1626534254@sss.pgh.pa.us>
On 2021-Jul-17, Tom Lane wrote:
> I've concluded that we should just document them (and am working
> on that right now). It's certainly true that there is a use-case
> for reading them: libpq does "SHOW transaction_read_only", for
> example. And since we've gone to the trouble of making SET of one
> of these equivalent to SET TRANSACTION, we should probably just
> document that it is.
Maybe include "SET NAMES" while at it? It drove me crazy when I found
out that was accepted, last year.
--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
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: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, bharath.rupireddyforpostgres@gmail.com, leiyanliang@highgo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17077: about three parameters in postgresql 13.3
In-Reply-To: <202107171724.hycens5f43ho@alvherre.pgsql>
* 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