Re: BUG #14041: transaction_read_only documentation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: jako(dot)andras(at)eik(dot)bme(dot)hu
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14041: transaction_read_only documentation
Date: 2016-04-28 01:55:48
Message-ID: 20160428015548.GB13281@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Mar 23, 2016 at 11:05:19AM +0000, jako(dot)andras(at)eik(dot)bme(dot)hu wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14041
> Logged by: Andras Jako
> Email address: jako(dot)andras(at)eik(dot)bme(dot)hu
> PostgreSQL version: 9.5.1
> Operating system: FreeBSD
> Description:
>
> http://www.postgresql.org/docs/9.5/static/hot-standby.html says: "Users will
> be able to tell whether their session is read-only by issuing SHOW
> transaction_read_only."
> http://www.postgresql.org/docs/9.5/static/sql-show.html says: "Available
> parameters are documented in Chapter 18 and on the SET reference page."
>
> But I can't find transaction_read_only mentioned nor in Chapter 18 nor on
> the SET reference page.

Yes, this is odd. This shows default_transaction_read_only:

http://www.postgresql.org/docs/9.5/static/runtime-config-client.html

but not transaction_read_only. I think we need to fix that.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Justin Noor 2016-04-28 03:30:13 Problem Running Post-Install Step. Installation May Not Complete Correctly. The Database Cluster Initialisation Failed.
Previous Message Joe Steffee 2016-04-27 23:25:03 Re: BUG #14117: psql and pg_dump commands should use ENV perl