Re: pgsql: Fix document bug regarding read only transactions.

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: ishii(at)postgresql(dot)org, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix document bug regarding read only transactions.
Date: 2017-06-15 01:41:04
Message-ID: 20170615.104104.1023962800974388504.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

> I think the correct fix would have been to change "update sequences"
> to "update temporary sequences", not to remove it.

Not sure. The paragraph tries to explain the difference between read
only transactions and standby.

---------------------------------------------------------------
In normal operation, “read-only” transactions are allowed to update
sequences and to use LISTEN, UNLISTEN, and 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.
---------------------------------------------------------------

Regarding sequences, the paragraph supposes the use case on standby in
that a normal sequence was created on primary then it gets updated on
standby (that was used be possible). For temporary sequences, this
scenario is totally meaningless since temporary sequences are not
replicated, nor cannot be created on standby either. So I think
referring to temporary sequences here is pointless.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-06-15 01:44:15 Re: pgsql: Fix document bug regarding read only transactions.
Previous Message Tom Lane 2017-06-15 01:21:51 Re: pgsql: Fix document bug regarding read only transactions.