| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Document bug regarding read only transactions |
| Date: | 2017-06-14 20:27:29 |
| Message-ID: | CA+TgmoaiCvpJa+d112iPRK192p1OUcUZdtUhrYDQapkJYKJHaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 13, 2017 at 10:08 PM, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> 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, <quote>read-only</> transactions are allowed to
> update sequences and to 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.
>
> This is plain wrong.
It used to be true. Tom changed it in commit
05d8a561ff85db1545f5768fe8d8dc9d99ad2ef7, back in 2010.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-06-14 21:32:06 | Re: WIP: Data at rest encryption |
| Previous Message | Robert Haas | 2017-06-14 20:24:12 | Re: RTE_NAMEDTUPLESTORE, enrtuples and comments |