From: Manu <manuelreyesbravo@gmail.com>
To: Ludvig Janiuk <ludvig.janiuk@proton.me>
Cc: Fujii Masao <masao.fujii@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: 42P16 error when dropping and adding column
Date: Thu, 24 Sep 2026 21:50:07 -0300
Message-ID: <179029740761.4042414.16720325941604136764@gmail.com> (raw)
In-Reply-To: <9221c3eb-2b4e-42f7-899c-61b59482a38b@proton.me>
References: <9221c3eb-2b4e-42f7-899c-61b59482a38b@proton.me>
Hi Ludvig,
Ludvig Janiuk <ludvig.janiuk@proton.me> wrote:
> I'm not familiar with the Postgres bug lifecycle - is there anything
> else I need to do? File a formal bug in some tracker? Or has that
> already happened?
Nothing else is needed from you. PostgreSQL has no separate bug
tracker: this thread on pgsql-bugs is the bug report, and it is already
archived where the committers look.
Fujii posted a patch (v1) in this thread, and it was tested against
master and REL_18_STABLE. As of today it is not committed yet. Once a
committer pushes it, the commit message usually links back to this
thread, and a fix for an 18 regression like this one normally goes into
the next 18.x minor release, where it shows up in the release notes.
If you want to follow it, watching this thread is enough. Thanks for
the clear report with a reproducer, it made the bisect straightforward.
Regards,
Manu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: manuelreyesbravo@gmail.com, ludvig.janiuk@proton.me, masao.fujii@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: 42P16 error when dropping and adding column
In-Reply-To: <179029740761.4042414.16720325941604136764@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox