Re: BUG #18803: ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18803: ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1
Date: 2025-02-11 20:55:32
Message-ID: CAL9smLALU5Er=3rjPe8Ou0uQbh-7diRBC-ZLtegjF404zELYaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Tom,

On Tue, Feb 11, 2025 at 5:33 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-bugs by date

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