public inbox for [email protected]  

help / color / mirror / Atom feed

From: yanliang lei <[email protected]>
To: Álvaro Herrera <[email protected]>
Cc: Srinath Reddy Sadipiralla <[email protected]>
Cc: [email protected]
Subject: Re:Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
Date: Fri, 12 Dec 2025 18:23:24 +0800 (CST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Thanks for replying .


in the postgresql 18 ，not null has “Constraint Name”，and this is a PostgreSQL 18  New Feature.


so , i think that: this problem(BUG #19351) is a bug.



At 2025-12-11 15:29:45, "Álvaro Herrera" <[email protected]> wrote:
>On 2025-Dec-10, Srinath Reddy Sadipiralla wrote:
>
>> ah... just after a quick code lookup, remembered that
>> "not null" is treated as a column property, which is a
>> flag in pg_attribute catalog table named as "attnotnull",
>
>This is no longer true in 18.
>https://www.enterprisedb.com/blog/changes-not-null-postgres-18
>
>-- 
>Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
>"Fundamental layering violations tend to bite you on tender
>parts of your anatomy."                          (Tom Lane)
>https://postgr.es/m/[email protected]

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re:Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox