Re: BUG #19866: acldefault() emits invalid UTF-8 for a high-bit "char" value

From: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
To: 1548140642(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19866: acldefault() emits invalid UTF-8 for a high-bit "char" value
Date: 2026-11-13 19:10:39
Message-ID: CAB8bMitNrSDhuzOTtce2pyTA+A9CPA=+xFB+z-ZCk_HaepMusw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

ср, 11 нояб. 2026 г. в 15:33, PG Bug reporting form <noreply(at)postgresql(dot)org
>:

>
> The issue was reproduced on PostgreSQL 18.6 and PostgreSQL 20devel on
> Linux/amd64.
>
> This occurs when acldefault() is called with the high-bit one-byte "char"
> value 0x80 as an invalid object type.
>
>
>
Hi, Milo!
On master this is already fixed by e8a3ee5b197

--
Regards,
Rachitskiy Andrey

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Manu 2026-11-13 19:54:56 Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp
Previous Message Andrey Rachitskiy 2026-11-13 18:43:31 Re: BUG #19600: pgcrypto crypt() can return text with invalid encoding