From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | iseki zero <admin(at)iseki(dot)space>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Questions about document "Concurrenry control" section |
Date: | 2024-10-09 14:51:16 |
Message-ID: | 35d3e799d47700dc217b1f211aa0e0d5f4de4e67.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2024-10-09 at 18:07 +0800, iseki zero wrote:
> I found it difficult to understanding some paragraph in the document
> "Concurrency control" section.
>
> > The Repeatable Read mode provides a rigorous guarantee that each
> transaction sees a completely stable view of the database. However, this
> view will not necessarily always be consistent with some serial (one at
> a time) execution of concurrent transactions of the same level. For
> example, even a read-only transaction at this level may see a control
> record updated to show that a batch has been completed but/not/see one
> of the detail records which is logically part of the batch because it
> read an earlier revision of the control record. Attempts to enforce
> business rules by transactions running at this isolation level are not
> likely to work correctly without careful use of explicit locks to block
> conflicting transactions.
>
> At:
> https://www.postgresql.org/docs/17/transaction-iso.html#XACT-REPEATABLE-READ:~:text=The%20Repeatable%20Read%20mode,to%20block%20conflicting%20transactions.
>
> Specifically, I can't understand the example.
I think this is referring to this example:
https://wiki.postgresql.org/wiki/SSI#Deposit_Report
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-10-09 15:15:54 | Re: pg_dump throwing segfault error during backup |
Previous Message | Ron Johnson | 2024-10-09 14:29:09 | Re: Disk is filling up with large files. How can I clean? |