Re: 42P16 error when dropping and adding column

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Manu <manuelreyesbravo(at)gmail(dot)com>
Cc: Ludvig Janiuk <ludvig(dot)janiuk(at)proton(dot)me>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: 42P16 error when dropping and adding column
Date: 2026-10-06 04:22:39
Message-ID: CAHGQGwGrHSCRjyJZxOD7Npt7oDuAKf8CjrhqZmQS9nwJfEPg9A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Sep 29, 2026 at 2:55 AM Manu <manuelreyesbravo(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Peter Geoghegan 2026-10-06 03:39:32 Re: BUG #19749: bpchar_ops declares equalimage although bpchar equality ignores trailing spaces