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

From: Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
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: 2025-12-14 17:00:16
Message-ID: CAFC+b6o75trAiX95J3GnX-UaAD+MiPvRdGDYy7P=npDQr5sUbw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Álvaro,

On Sat, Dec 13, 2025 at 6:14 PM Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:

>
> Yeah, that's fair -- we discussed this kind of behavior during
> development and I was unsure about being strict about it, so avoided it.
>
>
+1 , thanks for the patch.

This is mostly straightforward to fix, as attached (though the error
> message needs work),

I have reviewed the patch except the below things and
LGTM until now.

> but I hit a snag with multiple inheritance -- if
> you apply this patch, you'll see failures in the pg_dump and pg_upgrade
> tests. I don't have any ideas to fix this right now, but I'll keep
> thinking about it.
>

I need to look further into these parts,and will update once
I have something solid.

--
Thanks,
Srinath Reddy Sadipiralla
EDB: https://www.enterprisedb.com/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Haowu Ge 2025-12-15 01:23:02 Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
Previous Message T iv 2025-12-13 19:34:35 Cluster is not being created