From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | Tender Wang <tndrwang(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Can't find not null constraint, but \d+ shows that |
Date: | 2024-04-10 11:01:52 |
Message-ID: | 202404101101.c7brh2evkssj@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-Apr-10, jian he wrote:
> another related bug, in master.
>
> drop table if exists notnull_tbl1;
> CREATE TABLE notnull_tbl1 (c0 int not null, c1 int);
> ALTER TABLE notnull_tbl1 ADD CONSTRAINT Q PRIMARY KEY(c0, c1);
> \d+ notnull_tbl1
> ALTER TABLE notnull_tbl1 ALTER c0 DROP NOT NULL;
> ALTER TABLE notnull_tbl1 ALTER c1 DROP NOT NULL;
>
> "ALTER TABLE notnull_tbl1 ALTER c0 DROP NOT NULL;"
> should fail?
No, this should not fail, and it is working correctly in master. You
can drop the not-null constraint, but the column will still be
non-nullable, because the primary key still exists. If you drop the
primary key later, then the column becomes nullable. This is by design.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"El miedo atento y previsor es la madre de la seguridad" (E. Burke)
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2024-04-10 11:18:26 | Re: Slow catchup of 2PC (twophase) transactions on replica in LR |
Previous Message | Alvaro Herrera | 2024-04-10 10:54:13 | Re: Can't find not null constraint, but \d+ shows that |