From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: ERROR: no NOT NULL constraint found to drop |
Date: | 2023-04-10 07:55:28 |
Message-ID: | ZDPA8BJ4YgZymdoY@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Apr 10, 2023 at 03:16:06PM +0800, Richard Guo wrote:
> I run into error $subject with the query below:
>
> # create table t1 (c int primary key null unique);
> CREATE TABLE
> # create table t2 (like t1);
> CREATE TABLE
> # alter table t2 alter c drop not null;
> ERROR: no NOT NULL constraint found to drop
>
> This starts since e056c557ae. I guess this shouldn't happen since the
> comment says so.
>
> /* this shouldn't happen */
> elog(ERROR, "no NOT NULL constraint found to drop");
Thanks for the report. This is not the only issue that has been
pointed out with this patch, so it is going to be reverted if you look
around here:
/message-id/3863449.1681071102@sss.pgh.pa.us
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-04-10 13:46:59 | Re: ERROR: no NOT NULL constraint found to drop |
Previous Message | Richard Guo | 2023-04-10 07:16:06 | ERROR: no NOT NULL constraint found to drop |