Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: James Inform <james(dot)inform(at)pharmapp(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Euler Taveira <euler(at)eulerto(dot)com>
Subject: Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
Date: 2022-08-14 03:55:46
Message-ID: CAH2-Wzn9jjv22x-Vto-5xo_YJNuMWid0xuOGMcN+LYSXRk-PPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Aug 13, 2022 at 8:21 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Hmm, but if we're enlarging the buffer, doesn't that imply
> a new input value? Seems like invalidation must occur anyway.

Yeah, on second thought it should be invalidated anyway (I had to
check because the details of how we cache strxfrm() and strcoll() are
tricky). Even still, I think that we should just use repalloc for
this.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-08-14 04:10:55 Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
Previous Message Tom Lane 2022-08-14 03:21:04 Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation