Re: SKIP LOCKED assert triggered

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: SKIP LOCKED assert triggered
Дата
Msg-id 4030482.1641312930@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: SKIP LOCKED assert triggered  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: SKIP LOCKED assert triggered  (Simon Riggs <simon.riggs@enterprisedb.com>)
Список pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Pushed, thanks Simon for reporting this problem.

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));

?

I'd be inclined to format it more like the adjacent Assert, too.

            regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: SKIP LOCKED assert triggered
Следующее
От: Bharath Rupireddy
Дата:
Сообщение: Re: pg_walinspect - a new extension to get raw WAL data and WAL stats