pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Pavlo Golub <pavlo.golub@cybertec.at>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: `transaction_read_only` GUC undocumented
Date: Wed, 23 Jan 2019 14:54:40 +0900
Message-ID: <20190123055440.GI3873@paquier.xyz> (raw)
In-Reply-To: <18fa8fbf-f5a3-4e4b-b751-8b9da58c117c@email.android.com>
References: <20190123002536.GC3873@paquier.xyz>
	<18fa8fbf-f5a3-4e4b-b751-8b9da58c117c@email.android.com>

On Wed, Jan 23, 2019 at 06:18:58AM +0200, Pavlo Golub wrote:
> Yeah, why not. Could you please give me a hint where can I find
> details about it? Sources or commits?

(You may want to avoid HTML..)

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.
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (7+ messages)  latest in thread

Message-ID: <20190123055440.GI3873@paquier.xyz>
Permalink:  ../20190123055440.GI3873@paquier.xyz/
Also on:    postgresql.org/message-id/20190123055440.GI3873@paquier.xyz

 · 

reply

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, pavlo.golub@cybertec.at, pgsql-docs@lists.postgresql.org
  Subject: Re: `transaction_read_only` GUC undocumented
  In-Reply-To: <20190123055440.GI3873@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