Re: Potential G2-item cycles under serializable isolation
raf <raf@raf.org>
From: raf <raf@raf.org>
To: pgsql-bugs@lists.postgresql.org
Date: 2020-06-12T22:11:36Z
Lists: pgsql-bugs
Thomas Munro wrote: > + Access to the system catalogs is not done using the isolation level > + of the current transaction. This has the effect that newly created > + database objects such as tables become visible to concurrent Repeatable > + Read and Serializable transactions, even though their contents does not. "their contents does not" should be "their contents do not". cheers, raf
Commits
-
Doc: Add references for SI and SSI.
- 4c897197d793 9.5.23 landed
- 7295ac9c6c71 9.6.19 landed
- e2aca0d02d97 10.14 landed
- 648e56d3984d 11.9 landed
- eb1286413c0a 12.4 landed
- 4701efa9f741 13.0 landed
- 1575fbf1ac3c 14.0 landed
-
Improve comments for [Heap]CheckForSerializableConflictOut().
- 44eff2841059 13.0 landed
- 7aa4fb592530 14.0 landed
-
Avoid update conflict out serialization anomalies.
- 5940ffb22131 14.0 landed
- 6df7105e5d50 13.0 landed
- e620a38c23b9 12.4 landed
- dd616f2ec1c5 11.9 landed
- 19a6e1bc3083 10.14 landed
- e81dc2b7e2c4 9.6.19 landed
- c05f6b354ffe 9.5.23 landed
-
Implement genuine serializable isolation level.
- dafaa3efb75c 9.1.0 cited