Re: [19] Proposal: function markers to indicate collation/ctype sensitivity

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [19] Proposal: function markers to indicate collation/ctype sensitivity
Date: 2025-06-04 15:33:45
Message-ID: 9B5DB6E2-18D2-4106-84D4-1B0FBD1069E4@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Jeff,

On Jun 3, 2025, at 23:22, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:

> If we didn't have separate markers, we'd need to assume that all of
> those objects could be affected by a provider update.

I understand the need to trace these dependencies, but as a function developer with relatively modest understanding of collation nuances, I’m wondering how I’d know I needed these markers. It seems complicated. Which leads me to think that adoption would be low outside of core.

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-06-04 15:34:58 Re: Add tab-completion for ALTER TABLE ADD NOT NULL
Previous Message David E. Wheeler 2025-06-04 15:27:18 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part