Re: [HACKERS] Document bug regarding read only transactions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Document bug regarding read only transactions
Date
Msg-id CA+TgmoaiCvpJa+d112iPRK192p1OUcUZdtUhrYDQapkJYKJHaA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Document bug regarding read only transactions  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: [HACKERS] Document bug regarding read only transactions  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List 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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] WIP: Data at rest encryption