From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: h@husseinnasser.com
Subject: Transaction wraparound and read committed isolation level
Date: Sun, 19 Feb 2023 03:10:43 +0000
Message-ID: <167677624368.647177.14087162303276367700@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/routine-vacuuming.html
Description:
hey guys
thanks for the work you do we really appreciate it.
In the transaction wraparound section this statement is misleading and got
me really confused.
“a row version with an insertion XID greater than the current transaction's
XID is “in the future” and should not be visible to the current
transaction“
If the current transaction isolation level is read committed it absolutely
can see rows committed by future transactions with higher XIDs.
Would be cool to add a note.
this also bear the question that the wraparound isn’t really a problem with
default isolation level but more for higher levels such as repeatable read
and such.
please correct me if my understanding is incorrect.
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, h@husseinnasser.com
Subject: Re: Transaction wraparound and read committed isolation level
In-Reply-To: <167677624368.647177.14087162303276367700@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