| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction |
| Date: | 2023-03-07 01:16:37 |
| Message-ID: | 3777235.1678151797@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Tue, Mar 7, 2023 at 12:42 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2023-03-07 06:00:01 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |
| Previous Message | Thomas Munro | 2023-03-07 01:14:03 | Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction |