Re: Built-in CTYPE provider

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>, Noah Misch <noah(at)leadboat(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Built-in CTYPE provider
Date: 2024-07-05 17:13:09
Message-ID: bd5d55d8c9e9e4a4f167a3b89992c397f798d903.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2024-07-05 at 13:55 +0200, Daniel Verite wrote:
> When these versions get bumped, it seems like packagers could stick
> to
> previous versions by just overriding these.

That's an interesting point. It's actually easier for a packager to pin
Unicode to a specific version than to pin libc to a specific version.

> When doing that, are there any function that may have an immutability
> breakage problem with the built-in locale provider? (I would expect
> none).

Right, there wouldn't be any breakage without new data files.

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2024-07-05 17:35:43 Re: Partial aggregates pushdown
Previous Message Sami Imseih 2024-07-05 16:57:37 Re: Restart pg_usleep when interrupted