pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Jonathan S. Katz <jkatz@postgresql.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
Cc: rmt@lists.postgresql.org
Subject: Re: Move defaults toward ICU in 16?
Date: Wed, 3 May 2023 11:29:14 -0400
Message-ID: <6d3662d6-e150-34c5-6785-2cfdd2b8992f@postgresql.org> (raw)
In-Reply-To: <2497753.1681756418@sss.pgh.pa.us>
References: <20230217205009.4sy4lmmqanbhjsgb@awork3.anarazel.de>
	<558f794c351fb73596e4b05d96f66d01d56b4a50.camel@j-davis.com>
	<f2b896d1476915862b99c2514c298c052e048c57.camel@j-davis.com>
	<d62b2874-729b-d26a-2d0a-0d64f509eca4@enterprisedb.com>
	<438b15cf88c9c5cf0cf1c24bf7b835d6362a8e0c.camel@j-davis.com>
	<10bb0e53ba16e5865ea4d37575ee15d4df5dc043.camel@j-davis.com>
	<0ad3543a-40d9-17f9-794f-75ea0106544a@enterprisedb.com>
	<27767473241239ed7b518fc7c4c78d98e2376b3a.camel@j-davis.com>
	<d22a37cf-472d-cf05-4398-d370879ae6cb@enterprisedb.com>
	<82c4c816-06f6-d3e3-ba02-fca4a5cef065@enterprisedb.com>
	<ZD1INw6en0EUInYH@telsasoft.com>
	<c007f3c9a5f2866aa2c0b90680eb22cf9f5b58c3.camel@j-davis.com>
	<2497753.1681756418@sss.pgh.pa.us>

On 4/17/23 2:33 PM, Tom Lane wrote:
> Jeff Davis <pgsql@j-davis.com> writes:
>> Is now a reasonable time to check it in and see what breaks? It looks
>> like there are quite a few buildfarm members that specify neither --
>> with-icu nor --without-icu.
> 
> I see you just pinged buildfarm-members again, so I'd think it's
> polite to give people 24 hours or so to deal with that before
> you break things.

[RMT hat]

This thread has fallen silent and the RMT wanted to check in.

The RMT did have a brief discussion on $SUBJECT. We agree with several 
points that regardless of if/when ICU becomes the default collation 
provider for PostgreSQL, we'll likely have to flush out several issues. 
The question is how long we want that period to be before releasing the 
default.

Right now, and in absence of critical issues or objections, the RMT is 
OK with leaving in ICU as the default collation provider for Beta 1. If 
we're to revert back to glibc, we recommend doing this before Beta 2.

However, if there are strong objections to this proposal, please do 
state them.

Thanks,

Jonathan


Attachments:

  [application/pgp-signature] OpenPGP_signature (839B, ../6d3662d6-e150-34c5-6785-2cfdd2b8992f@postgresql.org/2-OpenPGP_signature)
  download

view thread (53+ messages)

Message-ID: <6d3662d6-e150-34c5-6785-2cfdd2b8992f@postgresql.org>
Permalink:  ../6d3662d6-e150-34c5-6785-2cfdd2b8992f@postgresql.org/
Also on:    postgresql.org/message-id/6d3662d6-e150-34c5-6785-2cfdd2b8992f@postgresql.org

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: jkatz@postgresql.org, tgl@sss.pgh.pa.us, pgsql@j-davis.com, pryzby@telsasoft.com, peter.eisentraut@enterprisedb.com, andres@anarazel.de, bruce@momjian.us, thomas.munro@gmail.com, robertmhaas@gmail.com, rmt@lists.postgresql.org
  Subject: Re: Move defaults toward ICU in 16?
  In-Reply-To: <6d3662d6-e150-34c5-6785-2cfdd2b8992f@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox