Re: BUG #18803: ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1 - Mailing list pgsql-bugs

From Marko Tiikkaja
Subject Re: BUG #18803: ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1
Date
Msg-id CAL9smLALU5Er=3rjPe8Ou0uQbh-7diRBC-ZLtegjF404zELYaw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18803: ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi Tom,

On Tue, Feb 11, 2025 at 5:33 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thanks for the clear report!  We've seen a few variants of this,
> and apparently yours is among the cases that are recently fixed.
> Trying this example on a fresh 16-tip build (more or less 16.7)
> just emits

That would be my bad.  I git grep'd the 16 branch but I thought it was
unrelated.  Thanks for the confirmation!


.m



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18804: LISTEN on channel fails with "could not access status of transaction"
Next
From: PG Bug reporting form
Date:
Subject: BUG #18805: A specific query on a hash partitioned table always causes a "signal 11: Segmentation fault" error.