Re: SKIP LOCKED assert triggered - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: SKIP LOCKED assert triggered
Date
Msg-id CANbhV-GzirR680VMMgq+imuAH11UgTY_Q01Byq5j0O2kasc-mg@mail.gmail.com
Whole thread Raw
In response to Re: SKIP LOCKED assert triggered  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 4 Jan 2022 at 16:15, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> > Pushed, thanks Simon for reporting this problem.

And causing another; my bad, apologies.

> Umm ...
>
>        Assert(TM_WouldBlock || !(tuple->t_data->t_infomask & HEAP_XMAX_INVALID));
>
> AFAICS, this assertion condition is constant-true,
> because TM_WouldBlock is a nonzero constant.  Perhaps you meant
>
>        Assert(result == TM_WouldBlock || !(tuple->t_data->t_infomask & HEAP_XMAX_INVALID));

Yes, I think that's what I meant.

-- 
Simon Riggs                http://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: generalized conveyor belt storage
Next
From: Thomas Munro
Date:
Subject: Re: daitch_mokotoff module