> 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 -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers