From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pavlo Golub <pavlo.golub@cybertec.at>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: `transaction_read_only` GUC undocumented
Date: Wed, 23 Jan 2019 15:14:22 +0900
Message-ID: <20190123061422.GK3873@paquier.xyz> (raw)
In-Reply-To: <4210.1548223651@sss.pgh.pa.us>
References: <20190123002536.GC3873@paquier.xyz>
<18fa8fbf-f5a3-4e4b-b751-8b9da58c117c@email.android.com>
<20190123055440.GI3873@paquier.xyz>
<4210.1548223651@sss.pgh.pa.us>
On Wed, Jan 23, 2019 at 01:07:31AM -0500, Tom Lane wrote:
> Michael Paquier <michael@paquier.xyz> writes:
>> transaction_read_only is listed in src/backend/utils/misc/guc.c, so we
>> could put a description close to default_transaction_read_only in
>> config.sgml, except that transaction_read_only sets the current
>> transaction's read-only status.
>
> Do we really want to document that? It's not the standard-approved
> way of making a transaction read-only.
i'd rather document them clearly rather than letting them around with
users guessing what they actually do (remember the recent thread about
replication parameter in connection strings). By the way, I can see
that transaction_deferrable and transaction_isolation are not around
either...
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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-docs@postgresql.org
Cc: michael@paquier.xyz, tgl@sss.pgh.pa.us, pavlo.golub@cybertec.at, pgsql-docs@lists.postgresql.org
Subject: Re: `transaction_read_only` GUC undocumented
In-Reply-To: <20190123061422.GK3873@paquier.xyz>
* 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