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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: marko(at)joh(dot)to
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 15:33:38
Message-ID: 2927186.1739288018@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Given this schema:
> ...
> Running this query:
> ...
> produces the following error:
> ERROR: wrong varnullingrels (b) (expected (b 4)) for Var 2/1

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

DO

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2025-02-11 16:26:26 BUG #18804: LISTEN on channel fails with "could not access status of transaction"
Previous Message Laurenz Albe 2025-02-11 14:20:24 Re: Major Version Upgrade failure due to orphan roles entries in catalog