| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | ludovitkramar <ludovitkramar(at)proton(dot)me> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG: SUBSTRING on TOASTed text returns "invalid byte sequence for encoding UTF8: 0xc3" |
| Date: | 2026-02-21 15:05:06 |
| Message-ID: | CAKFQuwYoHhmPDidGODjCmbs7uDXZePZz=ue4J0YcCjKi_GzYzw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Friday, February 20, 2026, ludovitkramar <ludovitkramar(at)proton(dot)me> wrote:
> Disclosure: This bug reproduction and report were generated with the
> assistance of Claude Opus 4.6, and reviewed by me.
>
>
> PostgreSQL version: 18.2-1 (Arch Linux package)
>
> SELECT version();
> PostgreSQL 18.2 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 15.2.1
> 20260209, 64-bit
>
You should modify your prompt to include looking for current news and bug
reports on the PostgreSQL website before writing up a new report.
https://www.postgresql.org/about/news/out-of-cycle-release-scheduled-for-february-26-2026-3241/
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-02-21 15:13:59 | Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists |
| Previous Message | Álvaro Herrera | 2026-02-21 13:45:31 | Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists |