Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>
Cc: yanliang lei <msdnchina(at)163(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
Date: 2026-02-03 11:40:44
Message-ID: 202602031139.fyestyplb4vu@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2026-Feb-02, Álvaro Herrera wrote:

> Here's the patch in v3, which I intend to push tomorrow morning to both
> 18 and master. (It backpatches cleanly). For 18 it will mean an ABI
> break due to the change to AdjustNotNullInheritance()'s signature,
> requiring a touch to .abi-compliance-history as well, but that comes
> later.

Pushed. I'm now going to wait for the failure in baza.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Computing is too important to be left to men." (Karen Spärck Jones)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-02-04 02:29:19 BUG #19392: PG_UPGRADE is non-functional on Windows
Previous Message Dmitry Kovalenko 2026-02-03 09:36:59 Re: BUG #19391: pg_ctl: the PID file "/xxxx/postmaster.pid" is empty