From: | Pantelis Theodosiou <ypercube(at)gmail(dot)com> |
---|---|
To: | hoanguyen2708(at)gmail(dot)com |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Wrong description in "13.2.1. Read Committed Isolation Level" |
Date: | 2017-10-19 12:30:01 |
Message-ID: | CAE3TBxzXJtQ_6gEoq0wciyEyPcwoBX0H62Dm+-6r==+KAvyhOg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Fri, Oct 13, 2017 at 12:17 PM, <hoanguyen2708(at)gmail(dot)com> wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/transaction-iso.html
> Description:
>
> In section "13.2.1. Read Committed Isolation Level" the document
> states that
> "it never sees either uncommitted data or changes committed during
> query
> execution by concurrent transactions" but this is exactly the same as
> "Repeatable Read Isolation Level".
They are not the same. Read Committed has:
> ... sees data committed before the *query* began; ...... changes
committed during *query execution* ...
but Repeatable Read has:
> ... sees data committed before the *transaction* began; ...... changes
committed during *transaction execution* ...
> Also in the last sentence of the
> paragraph it says "if other transactions commit changes after the
> first
> SELECT starts and before the second SELECT starts" meaning that it
> could see
> the commited data from other concurrent transaction which is completely
> contradict with the previous statement.
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-10-19 15:06:12 | Re: Incorrect link in release notes |
Previous Message | Magnus Hagander | 2017-10-19 11:56:55 | Re: Typo in word "password" |