Re: Transaction wraparound and read committed isolation level - Mailing list pgsql-docs

From Peter Geoghegan
Subject Re: Transaction wraparound and read committed isolation level
Date
Msg-id CAH2-WzmyWqbJvwdKchjsuAd86kYdwA-yGBMPbMnsr_C4m9xGWw@mail.gmail.com
Whole thread Raw
In response to Re: Transaction wraparound and read committed isolation level  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-docs
On Tue, Feb 21, 2023 at 9:46 AM Peter Geoghegan <pg@bowt.ie> wrote:
> All that you need is two statements within the same READ COMMITTED
> transaction, combined with a second concurrently executing
> transaction. The second transaction need only start after the first
> one (giving it a later XID), and then commit before the first
> transaction's second statement begins. Each RC statement gets its own
> snapshot, so the second statement in the first transaction can see any
> effects from the first transaction.

Correction: Each RC statement gets its own snapshot, so the second
statement in the first transaction can see any effects from the
*second* (now committed) transaction.

-- 
Peter Geoghegan



pgsql-docs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Transaction wraparound and read committed isolation level
Next
From: PG Doc comments form
Date:
Subject: Row Level Security Execution within the SQL Evaluation Pipeline