Re: Built-in CTYPE provider - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Built-in CTYPE provider
Date
Msg-id 1908b19c0a3a210935608635cad1b4eeb819c66f.camel@j-davis.com
Whole thread Raw
In response to Re: Built-in CTYPE provider  (Noah Misch <noah@leadboat.com>)
Responses Re: Built-in CTYPE provider
List pgsql-hackers
On Thu, 2024-07-11 at 05:50 -0700, Noah Misch wrote:
> > This is still marked as an open item for 17, but you've already
> > acknowledged[1] that no code changes are necessary in version 17.
>
> Later posts on the thread made that obsolete.  The next step is to
> settle the
> question at https://postgr.es/m/20240706195129.fd@rfd.leadboat.com. 
> If that
> conclusion entails a remedy, v17 code changes may be part of that
> remedy.

This is the first time you've mentioned a code change in version 17. If
you have something in mind, please propose it. However, this feature
followed the right policies at the time of commit, so there would need
to be a strong consensus to accept such a change.

Additionally, I started a discussion on version 18 policy that may also
resolve your concerns:

https://www.postgresql.org/message-id/d75d2d0d1d2bd45b2c332c47e3e0a67f0640b49c.camel@j-davis.com

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: PG_TEST_EXTRA and meson
Next
From: Nathan Bossart
Date:
Subject: Re: [PATCH] Refactor pqformat.{c,h} and protocol.h