Re: pgsql: Perform provider-specific initialization in new functions. - Mailing list pgsql-committers

From Jeff Davis
Subject Re: pgsql: Perform provider-specific initialization in new functions.
Date
Msg-id 2153399092d446bc1137eee5f70ad7af70e9039e.camel@j-davis.com
Whole thread
In response to Re: pgsql: Perform provider-specific initialization in new functions.  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-committers
On Mon, 2026-04-13 at 14:08 -0700, Jeff Davis wrote:

> That
> has two benefits:
>
> 1. Fixes your issue, because C_COLLATION_OID is always available.
> 2. Faster than a default collation based on libc or ICU.

I didn't detect any meaningful improvement here, probably because most
catalog cache lookups use columns with type NAME not TEXT.

But this still seems like a good idea on the grounds that, if we are
choosing an arbitrary deterministic collation for some internal
purpose, we should consistently choose the simplest and fastest one.

>
> I don't see a reason to backport this, but if someone else does then
> I
> could be convinced.

I plan to commit this soon.

I don't plan to backport unless someone sees a reason that it should be
backported (and if so, how far?).

Regards,
    Jeff Davis




pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: pgsql: doc PG 19 relnotes: add author and move items
Next
From: Álvaro Herrera
Date:
Subject: pgsql: Add missing initialization