Re: Repeatable Read Isolation Level "transaction start time"

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Wizard Brony <wizardbrony(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Repeatable Read Isolation Level "transaction start time"
Date: 2024-09-25 17:22:31
Message-ID: CAKAnmmLt2ezcf7-LgJkO_oeqK+Ei+XB6F3pHk2mnyadRq3corQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Sep 24, 2024 at 10:28 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> It's even looser than that, really: it's the first statement that
> requires an MVCC snapshot.

Hm....so why does "SELECT 1;" work as a transaction start marker then, as
opposed to "SHOW work_mem;", which does not? Do we simply consider anything
with a SELECT as needing a snapshot?

Cheers,
Greg

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2024-09-25 17:44:42 Re: Repeatable Read Isolation Level "transaction start time"
Previous Message Adrian Klaver 2024-09-25 15:36:13 Re: PgBackRest : Restore to a checkpoint shows further transactions