From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: anton.sidyakin@gmail.com
Subject: bad choice of the word in sentence
Date: Thu, 22 Jun 2023 18:38:37 +0000
Message-ID: <168745911769.2239590.6062411529242609290@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/transaction-iso.html
Description:
https://www.postgresql.org/docs/current/transaction-iso.html#XACT-READ-COMMITTED
Quote:
"<...>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. <...>"
"... changes committed during ..."
Don't you think this is bad choice of the word, especially while speaking
about "commiting transactions" in very same sentence?
Wouldn't it be better to say something like
<...> it never sees either uncommitted data or changes produced during query
execution by concurrent transactions. <...>
I mean, with read committed isolation level SELECT clearly can see changes
from concurrent transactions, if these transactions COMMITED.
In fact, you can read about that in few lines later:
"<...>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. <...>"
The sentences seem to contradict each other because of " it never sees ...
changes committed during ..."
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, anton.sidyakin@gmail.com
Subject: Re: bad choice of the word in sentence
In-Reply-To: <168745911769.2239590.6062411529242609290@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