On Wed, Jun 14, 2017 at 11:08 AM, Tatsuo Ishii <is...@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 -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers