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

From Peter Eisentraut
Subject Re: Rework of collation code, extensibility
Date
Msg-id 8d87e399-84ee-1cf2-5a07-1fb2e4f15400@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 06.01.23 08:04, Jeff Davis wrote:
> The existing code is not great, in my opinion: it doesn't have clear
> API boundaries, the comments are insufficient, and lots of special
> cases need to be handled awkwardly by callers. That style is hard to
> beat when it comes to the raw line count; but it's quite difficult to
> understand and work on.
> 
> I think my changes are an improvement, but obviously that depends on
> the opinion of others who are working in this part of the code. What do
> you think?

I think the refactoring that you proposed in the thread "Refactor to 
introduce pg_strcoll()." was on a sensible track.  Maybe we should try 
to get that done.  The multiple-ICU stuff is still experimental and has 
its own rather impressive thread, so I don't think it's sensible to try 
to sort that out here.




pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Strengthen pg_waldump's --save-fullpage tests
Next
From: Jelte Fennema
Date:
Subject: Re: [EXTERNAL] Re: [PATCH] Support using "all" for the db user in pg_ident.conf