| From: | "yanliang lei" <msdnchina(at)163(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | "Srinath Reddy Sadipiralla" <srinath2133(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re:Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. |
| Date: | 2025-12-12 10:23:24 |
| Message-ID: | 1259da72.9641.19b12163641.Coremail.msdnchina@163.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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" <alvherre(at)kurilemu(dot)de> 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/2818249.1748706121@sss.pgh.pa.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Veeranjaneya Vara Prasad Peddireddy | 2025-12-12 10:59:25 | Bug in sub-query |
| Previous Message | PG Bug reporting form | 2025-12-12 10:11:15 | BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list |