| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Document bug regarding read only transactions |
| Date: | 2017-06-14 02:41:02 |
| Message-ID: | CAB7nPqS_pH=+X7Dm4JK+6242j1DKW88+0S62ggA2sCPA969GSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 14, 2017 at 11:08 AM, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2017-06-14 03:18:02 | Re: Document bug regarding read only transactions |
| Previous Message | Craig Ringer | 2017-06-14 02:36:37 | Re: ICU support on Windows |