Horton

Re: Document bug regarding read only transactions

Michael Paquier <michael.paquier@gmail.com>

View thread View on postgr.es
From: Michael Paquier <michael.paquier@gmail.com>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2017-06-14T02:41:02Z
Lists: pgsql-hackers 
On Wed, Jun 14, 2017 at 11:08 AM, Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
>     <para>
>      In normal operation, <quote>read-only</> transactions are allowed to
> -    update sequences and to use <command>LISTEN</>, <command>UNLISTEN</>, and
> +    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.

Your modification does not look completely correct to me either.
Temporary sequences can be updated in read-only transactions. I think
that the page listing the sequence-related functions should as well
mention those restrictions for nextval() and setval().
-- 
Michael

Commits

  1. Fix document bug regarding read only transactions.

  2. Clean up handling of XactReadOnly and RecoveryInProgress checks.