From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | h(at)husseinnasser(dot)com |
Subject: | Transaction wraparound and read committed isolation level |
Date: | 2023-02-19 03:10:43 |
Message-ID: | 167677624368.647177.14087162303276367700@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Kirk Wolak | 2023-02-19 20:55:59 | Re: February 9th, 2023 Release links to a missing page |
Previous Message | David G. Johnston | 2023-02-17 17:09:34 | Re: unclear syntax explanation for multiple window definitions in a SELECT query |