Re: Is NEW.ctid usable as table_tuple_satisfies_snapshot?

From: Kaiting Chen <ktchen14(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Is NEW.ctid usable as table_tuple_satisfies_snapshot?
Date: 2023-05-26 18:41:23
Message-ID: CA+CLzG-NLPv-6LkpZybXHnGt_U6w75DgAJ_8v7g_UOWrYQfqxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 26, 2023 at 12:49 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> > Just to clarify, there's no way for SELECT FROM foo WHERE ctid = NEW.ctid
> > to return a row that ordinary wouldn't be visible right? There's no magic
> > going on with the qual on ctid that skips a visibility check right?
>
> No, a ctid test isn't magic in that way; nodeTidscan.c applies the
> same snapshot check as any other relation scan.
>

Okay thanks!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2023-05-26 18:47:02 Re: Order changes in PG16 since ICU introduction
Previous Message Jeff Davis 2023-05-26 17:43:09 Re: pg_collation.collversion for C.UTF-8