From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: mossa708496@gmail.com
Subject: docs issue in transactions section
Date: Fri, 02 Jul 2021 19:11:15 +0000
Message-ID: <162525307568.700.736681752884243253@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/transaction-iso.html
Description:
13.2.1. Read Committed Isolation Level
Read Committed is the default isolation level in PostgreSQL. When a
transaction uses this isolation level, a SELECT query (without a FOR
UPDATE/SHARE clause) sees only data committed before the query began; it
never sees either uncommitted data or changes committed during query
execution by concurrent transactions. In effect, a SELECT query sees a
snapshot of the database as of the instant the query begins to run. However,
SELECT does see the effects of previous updates executed within its own
transaction, even though they are not yet committed. Also note that two
successive SELECT commands can see different data, even though they are
within a single transaction, if other transactions commit changes after the
first SELECT starts and before the second SELECT starts.
I don't understand this very clearly: " it never sees either uncommitted
data or changes committed during query execution by concurrent
transactions." and this statement " Also note that two successive SELECT
commands can see different data, even though they are within a single
transaction, if other transactions commit changes after the first SELECT
starts and before the second SELECT starts."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, mossa708496@gmail.com
Subject: Re: docs issue in transactions section
In-Reply-To: <162525307568.700.736681752884243253@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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