Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q6cUo-00045O-3b for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Jun 2023 19:37:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q6cUm-0003ac-Nl for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Jun 2023 19:37:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q6cUm-0003aA-EJ for pgsql-hackers@lists.postgresql.org; Tue, 06 Jun 2023 19:37:32 +0000 Received: from mail-lj1-x236.google.com ([2a00:1450:4864:20::236]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q6cUj-000dY8-Hk for pgsql-hackers@lists.postgresql.org; Tue, 06 Jun 2023 19:37:31 +0000 Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-2b1afe57bdfso61593721fa.0 for ; Tue, 06 Jun 2023 12:37:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686080249; x=1688672249; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Uz70DZC6DiyhyQinwLy2sSErkj4BgUkOUrBqjYn1jY4=; b=QhtplpEiT3bVPVakC5NC9d44PRwX35+AQwPjPQuwvcohssRT9QC769pjgomNwDjphY TQzEew2PceKl75U2kurw8JooUclZRbKRRr8b+0os/WMB0ac/JK30RFxj96vsF3KYX84K 667rh/lW4D4s2AoDfZVslizN6ZdJZLbEWLPogI6+JDWXZzM3hWaNlcByeKjif7Nilg5X ABtXtWcVqSNZMkfUknfEzzLpuNMmNnwjGwUSKraN8drGiUvSlzPJ8FrdX7BrfLnsrW3R XhZ2Ay8QSpeQq1fqPKo+SmY++Y3iNtA2qsmz36Gx0dRU6RzhpOQb8NWePDhBPJw7kl31 fmqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686080249; x=1688672249; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Uz70DZC6DiyhyQinwLy2sSErkj4BgUkOUrBqjYn1jY4=; b=gBTLWGOiJ+69pqgpMfQf+EV6TLamwBB/3VDuJtAso12B6TKp3EI4q9e3ao4Luuwmba J1dtwL4uCXRZvfO+h5OUXLSSMpdktDkCzRzrz+GFzZmuESPr/QLuwVjg7UOwwglWUnmS iYbNQlQToignSXrHie2Fe6tau0vKCGrrWz4se6JYlQPsOWnFT5aYAVDOEfwiaq/7gCg1 N3Tdkt0iCV4jMWDBOzhTPazVXIozZLIptIFhnwFGIYfHSgVbf+10JekB4bzvvZp+eDbf SXyb1DT6J2XMFM+ULgl0Vr1BzhAercyiqbYoG9c4pOaxQS7fdOpuGqJcAkQ1hBgXpx5M vN5g== X-Gm-Message-State: AC+VfDzTbUIzo8XfR6qvYSJu3H7gSdHxQuQYkTZ1H+eaD6Jkp49usAzC iPto30G2bLFtPW1FhxXMUPD/Mo0fGU+nU39YN3hVgVhU X-Google-Smtp-Source: ACHHUZ4uWj2eRuIoQLneirgs76x8UtAZxjBQ53O4S8GraCuT2Pmx/XrWg7hvRV8M/BVKB76AifYJ6LiHGORxZyhR+RU= X-Received: by 2002:a2e:9d5a:0:b0:2af:1262:e918 with SMTP id y26-20020a2e9d5a000000b002af1262e918mr1377382ljj.36.1686080248501; Tue, 06 Jun 2023 12:37:28 -0700 (PDT) MIME-Version: 1.0 References: <45f0cd77-9c85-4c5e-9396-adbccdb635e2@manitou-mail.org> <221408.1686079526@sss.pgh.pa.us> In-Reply-To: <221408.1686079526@sss.pgh.pa.us> From: Robert Haas Date: Tue, 6 Jun 2023 15:37:17 -0400 Message-ID: Subject: Re: Order changes in PG16 since ICU introduction To: Tom Lane Cc: Joe Conway , Jeff Davis , Daniel Verite , Peter Eisentraut , Andrew Gierth , pgsql-hackers@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Jun 6, 2023 at 3:25=E2=80=AFPM Tom Lane wrote: > Joe Conway writes: > > On 6/6/23 15:18, Jeff Davis wrote: > >> The locale "C" is a special case, documented as a non-locale. So, if > >> LOCALE/--locale apply to ICU, then either ICU needs to handle locale > >> "C" in the expected way (v8 patch series); or when we see locale "C" w= e > >> need to somehow change the provider into something that can handle it > >> (v6 patch series changes it to the "none" provider). > > > +1 to the latter approach > > Also +1, except that I find "none" a rather confusing choice of name. > There *is* a provider, it's just PG itself not either libc or ICU. > I thought Joe's suggestion of "internal" made more sense. Or perhaps "builtin" or "postgresql". I'm just thinking that "internal" as a type name kind of means "you shouldn't be touching this from SQL" and we don't want to give people the idea that the "C" locale isn't something you should use. --=20 Robert Haas EDB: http://www.enterprisedb.com