Thread: [DOCS] Wrong description in "13.2.1. Read Committed Isolation Level"

[DOCS] Wrong description in "13.2.1. Read Committed Isolation Level"

From
hoanguyen2708@gmail.com
Date:
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". 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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Wrong description in "13.2.1. Read Committed Isolation Level"

From
Pantelis Theodosiou
Date:


On Fri, Oct 13, 2017 at 12:17 PM, <hoanguyen2708@gmail.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 &quot;13.2.1. Read Committed Isolation Level&quot; the document states that
&quot;it never sees either uncommitted data or changes committed during query
execution by concurrent transactions&quot; but this is exactly the same as
&quot;Repeatable Read Isolation Level&quot;.

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 &quot;if other transactions commit changes after the first
SELECT starts and before the second SELECT starts&quot; 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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs