From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Order changes in PG16 since ICU introduction |
Date: | 2023-06-06 20:00:55 |
Message-ID: | 3e51d7f8-284e-29d5-39c9-3b7d6b4a53dc@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/6/23 3:56 PM, Joe Conway wrote:
> On 6/6/23 15:55, Tom Lane wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> On Tue, Jun 6, 2023 at 3:25 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>> Also +1, except that I find "none" a rather confusing choice of name.
>>>> There *is* a provider, it's just PG itself not either libc or ICU.
>>>> I thought Joe's suggestion of "internal" made more sense.
>>
>>> Or perhaps "builtin" or "postgresql".
>>
>> Either OK by me
>
> Same here
Since we're bikeshedding, "postgresql" or "builtin" could make it seem
to a (app) developer that these may be recommended options, as we're
trusting PostgreSQL to make the best choices for us. Granted, v16 is
(theoretically) defaulting to ICU, so that choice is made, but the
unsuspecting developer could make a switch based on that naming.
However, I don't have a strong alternative -- I understand the concern
about "internal", so I'd be OK with "postgresql" unless a better name
appears.
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2023-06-06 20:11:32 | Re: Assert failure of the cross-check for nullingrels |
Previous Message | Alvaro Herrera | 2023-06-06 20:00:09 | Re: Cleaning up nbtree after logical decoding on standby work |