| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part |
| Date: | 2025-05-24 16:08:18 |
| Message-ID: | D57D3B5E-AF55-4F7F-9E55-FE06EE8ED811@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 23, 2025, at 13:52, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I assume you mean that they’re set at initdb time, so there’s no mutability concern?
>
> Yeah, I think Peter's right and I'm wrong. Obviously this ties into
> our philosophical debate about how immutable is immutable. But as
> long as the functions only depend on locale settings that are fixed
> at database creation, I think it's okay to consider them immutable.
>
> If you were, say, depending on LC_NUMERIC, it would clearly be unsafe
> to consider that immutable, so I'm not quite sure if this is the end
> of the discussion. But for what's mentioned in the thread title,
> I think we only care about LC_CTYPE.
Oh, so maybe all this is moot, and Florents can go ahead and add support for the functions to the non-_tz functions?
Should there be some sort of inventory of what functions can be used in what contexts?
D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florents Tselai | 2025-05-24 16:51:32 | Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part |
| Previous Message | Sami Imseih | 2025-05-24 14:35:24 | Re: queryId constant squashing does not support prepared statements |