| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | h(at)husseinnasser(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Transaction wraparound and read committed isolation level |
| Date: | 2023-02-21 17:49:31 |
| Message-ID: | CAH2-WzmyWqbJvwdKchjsuAd86kYdwA-yGBMPbMnsr_C4m9xGWw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Tue, Feb 21, 2023 at 9:46 AM Peter Geoghegan <pg(at)bowt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2023-02-21 21:25:41 | Row Level Security Execution within the SQL Evaluation Pipeline |
| Previous Message | Peter Geoghegan | 2023-02-21 17:46:29 | Re: Transaction wraparound and read committed isolation level |