| From: | Ludvig Janiuk <ludvig(dot)janiuk(at)proton(dot)me> |
|---|---|
| To: | Manu <manuelreyesbravo(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: 42P16 error when dropping and adding column |
| Date: | 2026-09-25 14:06:08 |
| Message-ID: | a2a8d6dc-762b-4597-a708-bd71fd44a79c@proton.me |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Okay, thank you.
Best regards,
Ludvig Janiuk
On 2026-09-25 02:50, Manu wrote:
> Hi Ludvig,
>
> Ludvig Janiuk <ludvig(dot)janiuk(at)proton(dot)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
--
//Ludvig Janiuk
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manu | 2026-09-25 15:38:08 | Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0 |
| Previous Message | shihao zhong | 2026-09-25 13:35:37 | Re: BUG #19699: LIKE with a trailing escape fails to raise SQLSTATE 22025 for empty input |