From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | swehren(at)gmail(dot)com |
Cc: | "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Repeatable Read Table Reference |
Date: | 2016-05-25 16:23:29 |
Message-ID: | CACjxUsPU060OkZ-dn9ZfZ0oiWbu_w--H0wiNvhjeipZPrBiGCw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, May 24, 2016 at 3:38 PM, <swehren(at)gmail(dot)com> wrote:
> In the documentation for Repeatable Read on this page:
>
> https://www.postgresql.org/docs/current/static/transaction-iso.html
>
> The documentation says, "This is a stronger guarantee than is required by
> the SQL standard for this isolation level, and prevents all of the phenomena
> described in Table 13-1."
>
> Since the Serialization Anomaly was added to the table in this commit
> (https://github.com/postgres/postgres/commit/23c33198b961f27c80655a7cf439d49ef5a1833d#diff-a85793bf153f1f44870606f9695bc33c)
> that statement is no longer true if I understand the documentation
> correctly. Here's a brief patch to tweak that sentence.
Pushed. Thanks!
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | 星合 拓馬 | 2016-05-26 08:45:41 | log_min_autovacuum_duration parameter is incorrect |
Previous Message | Tsunakawa, Takayuki | 2016-05-25 00:01:20 | Re: Mention pg_reload_conf() in ALTER SYSTEM page |