Re: Rework of collation code, extensibility - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Rework of collation code, extensibility
Date
Msg-id 75c4b010-b15c-86d1-fde6-fa6f91de0e1d@enterprisedb.com
Whole thread Raw
In response to Re: Rework of collation code, extensibility  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Rework of collation code, extensibility
List pgsql-hackers
On 27.01.23 00:47, Jeff Davis wrote:
> I'm hoping to commit 0002 and 0003 soon-ish, maybe a week or two,
> please let me know if you want me to hold off. (I won't commit the GUCs
> unless others find them generally useful; they are included here to
> more easily reproduce my performance tests.)

I have looked a bit at 0002 and 0003.  I like the direction.  I'll spend 
a bit more time reviewing it in detail.  It moves a lot of code around.

I don't know to what extent this depends on the abbreviated key GUC 
discussion.  Does the rest of this patch set depend on this?




pgsql-hackers by date:

Previous
From: "wangw.fnst@fujitsu.com"
Date:
Subject: RE: [PATCH] Reuse Workers and Replication Slots during Logical Replication
Next
From: David Rowley
Date:
Subject: Re: heapgettup() with NoMovementScanDirection unused in core?