Horton

Re: Document bug regarding read only transactions

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-06-14T20:27:29Z
Lists: pgsql-hackers 
On Tue, Jun 13, 2017 at 10:08 PM, Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
> In https://www.postgresql.org/docs/10/static/hot-standby.html#hot-standby-users
>
> It is explained that read only transactions (not in standby) allow to
> update sequences.
>
>     In normal operation, <quote>read-only</> transactions are allowed to
>     update sequences and to use <command>LISTEN</>, <command>UNLISTEN</>, and
>     <command>NOTIFY</>, so Hot Standby sessions operate under slightly tighter
>     restrictions than ordinary read-only sessions.  It is possible that some
>     of these restrictions might be loosened in a future release.
>
> This is plain wrong.

It used to be true.  Tom changed it in commit
05d8a561ff85db1545f5768fe8d8dc9d99ad2ef7, back in 2010.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Fix document bug regarding read only transactions.

  2. Clean up handling of XactReadOnly and RecoveryInProgress checks.