Re: Collation & ctype method table, and extension hooks

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Collation & ctype method table, and extension hooks
Date: 2024-12-20 05:48:54
Message-ID: 0bed0042-ac43-4d3f-a9c1-7235b41e8b33@proxel.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/5/24 1:21 AM, Jeff Davis wrote:
>> = v9-0003-Move-code-for-collation-version-into-provider-spe.patch
>>
>> Moves some code from pg_collate.c into provider specific files.
>
> I agree with the general idea, but it seems we are accumulating a lot
> of provider-specific functions. Should we define a provider struct with
> its own methods?
>
> That would be a good step toward making the provider catalog-driven.
> Even if we don't support CREATE LOCALE PROVIDER, having space in the
> catalog would be a good place to track the provider version.

Yeah, that was my idea too but I just have not gotten around to it yet.

>> = v9-0004-Move-ICU-database-encoding-check-into-validation-.patch
>
> This seems to be causing a test failure in 020_createdb.pl.

Thanks, I have attached a fixup commit for this.

Andreas

Attachment Content-Type Size
0001-fixup-Move-ICU-database-encoding-check-into-validati.patch text/x-patch 865 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2024-12-20 06:00:00 Re: per backend I/O statistics
Previous Message Amit Kapila 2024-12-20 05:36:47 Re: Skip collecting decoded changes of already-aborted transactions