Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
Date
Msg-id 3777235.1678151797@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-bugs
Thomas Munro <thomas.munro@gmail.com> writes:
> On Tue, Mar 7, 2023 at 12:42 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> What if they both touched/modified a shared catalog?

> I was assuming that that would already skip all predicate locking because:

> /*
>  * Does this relation participate in predicate locking? Temporary and system
>  * relations are exempt.
>  */

Oh, I'd forgotten about that.

> If we ever wanted to use SSI on catalogs, or allow shared relations
> that aren't catalogs, or allow cross-database access, then this
> optimisation wouldn't fly.

I suppose there are some gotchas in the way of making that happen,
so okay.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger