From: | Maciek Sakrejda <maciek(at)pganalyze(dot)com> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [19] Proposal: function markers to indicate collation/ctype sensitivity |
Date: | 2025-06-04 15:48:23 |
Message-ID: | CADXhmgQBd__3t0YQC9M5hxV98emUdN0TBoTA2VgbkP+TdTwS=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 4, 2025 at 8:34 AM David E. Wheeler <david(at)justatheory(dot)com> wrote:
> 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.
That was my first thought as well. But my second thought was: does
that matter? There are substantial benefits to having this for just
core functions, no?
Thanks,
Maciek
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2025-06-04 15:53:53 | Re: [19] Proposal: function markers to indicate collation/ctype sensitivity |
Previous Message | Mankirat Singh | 2025-06-04 15:45:46 | Re: ABI Compliance Checker GSoC Project |