Re: 42P16 error when dropping and adding column - Mailing list pgsql-bugs

From Fujii Masao
Subject Re: 42P16 error when dropping and adding column
Date
Msg-id CAHGQGwGrHSCRjyJZxOD7Npt7oDuAKf8CjrhqZmQS9nwJfEPg9A@mail.gmail.com
Whole thread
In response to Re: 42P16 error when dropping and adding column  (Manu <manuelreyesbravo@gmail.com>)
List pgsql-bugs
On Tue, Sep 29, 2026 at 2:55 AM Manu <manuelreyesbravo@gmail.com> wrote:
> No case in the set errors on v2 while succeeding on unpatched master or
> REL_18.  The scenarios where a primary key still cannot be added (ONLY
> on an inheritance parent, a column that already holds a null row, a
> redundant named NOT NULL on a column that already has one) error
> identically on all three.  master and REL_18 give the same result on
> every case, and make check passes on both.

Thanks for the test! I've pushed the patch.

Regards,


--
Fujii Masao



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #19749: bpchar_ops declares equalimage although bpchar equality ignores trailing spaces
Next
From: Narayanan Venkateswaran
Date:
Subject: Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses