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

From Thomas Munro
Subject Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
Date
Msg-id CA+hUKGKRkLpPUEECYwdp8s8TPeDfzwTLi7Q_-H9t+RCGC6_ArA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-bugs
On Thu, Mar 9, 2023 at 9:00 AM Alexander Lakhin <exclusion@gmail.com> wrote:
> Just in case you find a test for the fix useful, maybe the attached
> patch could be added to the commit.
> (It triggers the assert on unpatched master.)

I was wondering about that.  I like the test and I was using exactly
that + also some other techniques while working on the fix, but the
point of that particular test spec is to show a variation of the
standard example from the read-only-anomaly paper.  Hmm, yeah, that's
not a problem, I can just add the extra schedule with a comment to
explain.  Will do.  Thanks!



pgsql-bugs by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
Next
From: Thomas Munro
Date:
Subject: Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction