Re: Crash issue in PG18.5 regression

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, "Masashi Kamura (Fujitsu)" <kamura(dot)masashi(at)fujitsu(dot)com>, "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: Crash issue in PG18.5 regression
Date: 2026-08-11 17:02:57
Message-ID: 2401224.1786467777@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2026-08-11 12:41:49 +0300, Heikki Linnakangas wrote:
>> Like the attached.

> I wonder if we also ought to do something about the other uses of
> pg_locale_t->info.lt in pg_locale_libc.c? That's at least strncoll_libc(),
> strnxfrm_libc(). I think all the in-core callers guard them, but the
> protection seems mighty far away in some cases.

We don't have a lot of time to think about this, and AFAICS the
security patch only added calls to pg_strupper and pg_strlower.
So as long as those are protected I'm content to ship.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-08-11 17:25:01 CREATE INDEX vs. TOAST table stats
Previous Message Andres Freund 2026-08-11 16:55:18 Re: Crash issue in PG18.5 regression