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: yanliang lei <msdnchina(at)163(dot)com>
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 15:01:53
Message-ID: 202512121501.pmpgh7tiz53e@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2025-Dec-12, yanliang lei wrote:

> 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.

Did you read my other reply?
https://www.postgresql.org/message-id/202512110716.jpbcheffhdow%40alvherre.pgsql

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Right now the sectors on the hard disk run clockwise, but I heard a rumor that
you can squeeze 0.2% more throughput by running them counterclockwise.
It's worth the effort. Recommended." (Gerry Pourwelle)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Álvaro Herrera 2025-12-12 15:10:48 Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name.
Previous Message Veeranjaneya Vara Prasad Peddireddy 2025-12-12 10:59:25 Bug in sub-query