Date: Fri, 25 Sep 2026 14:06:08 +0000
To: Manu <manuelreyesbravo@gmail.com>
From: Ludvig Janiuk <ludvig.janiuk@proton.me>
Cc: Fujii Masao <masao.fujii@gmail.com>, pgsql-bugs@lists.postgresql.org
Subject: Re: 42P16 error when dropping and adding column
Message-ID: <a2a8d6dc-762b-4597-a708-bd71fd44a79c@proton.me>
In-Reply-To: <179029740761.4042414.16720325941604136764@gmail.com>
References: <9221c3eb-2b4e-42f7-899c-61b59482a38b@proton.me>
 <179029740761.4042414.16720325941604136764@gmail.com>
Feedback-ID: 90025008:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/a2a8d6dc-762b-4597-a708-bd71fd44a79c%40proton.me>
Precedence: bulk

Okay, thank you.

Best regards,
Ludvig Janiuk

On 2026-09-25 02:50, Manu wrote:
> 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

--=20
//Ludvig Janiuk