From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Repeatable Read Isolation Level "transaction start time" |
Date: | 2024-09-25 17:50:33 |
Message-ID: | CANzqJaBjwtzLg_bZHkokUJbtA8gy6RpHjirfdBH9OJGfn5=tmw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Sep 25, 2024 at 1:45 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
>
>
> On 9/25/24 10:22 AM, Greg Sabino Mullane wrote:
> > On Tue, Sep 24, 2024 at 10:28 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
> > <mailto: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?
>
>
> SELECT some_func();
>
> Where some_func() does something that requires a snapshot.
>
>
But why does "SELECT 1;" need a snapshot? Heck, why does "SELECT
<immutable>;" need a snapshot?
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> crustacean!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-09-25 17:53:37 | Re: Repeatable Read Isolation Level "transaction start time" |
Previous Message | Adrian Klaver | 2024-09-25 17:44:42 | Re: Repeatable Read Isolation Level "transaction start time" |