> It used to be true. Tom changed it in commit
> 05d8a561ff85db1545f5768fe8d8dc9d99ad2ef7, back in 2010.
Thank you for the info. For a record, I will add it to the commit
message.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.
On Tue, Jun 13, 2017 at 10:08 PM, Tatsuo Ishii 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, read-only transactions are allowed t
> Your modification does not look completely correct to me either.
> Temporary sequences can be updated in read-only transactions.
Not sure. Temporary sequences are meaningless on standby because
"create temporary sequence" command cannot be executed on standby
anyway (and temporary sequence are n
On Wed, Jun 14, 2017 at 11:08 AM, Tatsuo Ishii wrote:
>
> In normal operation, read-only transactions are allowed to
> -update sequences and to use LISTEN, UNLISTEN, and
> +use LISTEN, UNLISTEN, and
> NOTIFY, so Hot Standby sessions operate under slightly
> tighter
> r
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, read-only transactions are allowed to
update sequences and to use LISTEN, UNLISTEN, and
NOTIFY,
