Re: [HACKERS] Document bug regarding read only transactions - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: [HACKERS] Document bug regarding read only transactions
Date
Msg-id 20170614.121802.1997847422348064392.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: [HACKERS] Document bug regarding read only transactions  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
> 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 not replicated to standby of
course).

> I think
> that the page listing the sequence-related functions should as well
> mention those restrictions for nextval() and setval().

If we do so, ANALYZE, VACUUM, LISTEN and NOTIFY man pages should also
be updated to mention that they can be executed in read only
transaction but not in standby servers. I'm not sure it's worth the
trouble. Moreover, that will create maintenance headache once we
decide to remove some of the restrictions, because we need to update
multiple places in the doc.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Document bug regarding read only transactions
Next
From: Ashutosh Sharma
Date:
Subject: Re: [HACKERS] ICU support on Windows