pg.ddx.io pgsql-docs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Wrong description in "13.2.1. Read Committed Isolation Level" 2+ messages / 2 participants [nested] [flat]
* Wrong description in "13.2.1. Read Committed Isolation Level" @ 2017-10-13 11:17 hoanguyen2708@gmail.com 0 siblings, 1 reply; 2+ messages in thread From: hoanguyen2708@gmail.com @ 2017-10-13 11:17 UTC (permalink / raw) To: pgsql-docs 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 ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Wrong description in "13.2.1. Read Committed Isolation Level" @ 2017-10-19 12:30 Pantelis Theodosiou <ypercube@gmail.com> parent: hoanguyen2708@gmail.com 0 siblings, 0 replies; 2+ messages in thread From: Pantelis Theodosiou @ 2017-10-19 12:30 UTC (permalink / raw) To: hoanguyen2708@gmail.com; +Cc: pgsql-docs 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 "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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-docs > ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2017-10-19 12:30 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2017-10-13 11:17 Wrong description in "13.2.1. Read Committed Isolation Level" hoanguyen2708@gmail.com 2017-10-19 12:30 ` Pantelis Theodosiou <ypercube@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox