Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: 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-08 11:57:20
Message-ID: CA+hUKGKT1RCYcy_p8RKGs0C5-8c2=J38xMOcYTxsPL=x6sr-cA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Mar 7, 2023 at 12:39 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Scratch that. I like the more ambitious idea better. I originally
> thought it would be less back-patchable, but that's nonsense -- this
> was a straight up thinko in ancient commit bdaabb9b and we should just
> fix it properly. That is, we should treat this case as a
> generalisation of the the PredXact->WritableSxactCount == 0 case, it's
> just that we had to do more work to figure that out. Here's a patch
> like that.

Here's a better version. I plan to push this tomorrow if there are no
objections.

Attachment Content-Type Size
v4-0001-Fix-race-in-SERIALIZABLE-READ-ONLY.patch text/x-patch 3.9 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-03-08 15:50:23 Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
Previous Message Francisco Olarte 2023-03-08 09:55:36 Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"