Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uN70I-00C3Uo-BB for pgsql-general@arkaria.postgresql.org; Thu, 05 Jun 2025 09:35:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uN70F-006a3Z-Fo for pgsql-general@arkaria.postgresql.org; Thu, 05 Jun 2025 09:35:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uN70F-006a3Q-4p for pgsql-general@lists.postgresql.org; Thu, 05 Jun 2025 09:35:15 +0000 Received: from mail-qk1-x731.google.com ([2607:f8b0:4864:20::731]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uN70B-000MFk-38 for pgsql-general@postgresql.org; Thu, 05 Jun 2025 09:35:12 +0000 Received: by mail-qk1-x731.google.com with SMTP id af79cd13be357-7d0997d3ac7so84459085a.2 for ; Thu, 05 Jun 2025 02:35:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749116111; x=1749720911; darn=postgresql.org; 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=O0WVqpx4pzsn2g+f2/hxM0olho/ITNTWEYPLGB0lS6M=; b=dLZ7c+BhxvBtO6qNKWWv0xLkPw2C9pc7yN9NV5nQcebhYWvMGR8dtdc6sqmqWqo+7W p2IbF/au6Hzm91uU4Qj22e3opncIGRiSe0tZjtaFEQHdS/W123iO2izuVqpDjLGQURZh K8fmfAaKWndhB0vTpbjSGIQxekB4P+WW9f7xtCzG4jxTTgIVmgTu+jNxXnP3YBrq+bva yLQWJUQtZ9azaNktURBQChUa3TvrO+aTbRT0e7/Iulx7ve4z2D5wUdLQAC86egjwIx4w ktXep2621t0vhLcMp7twD4JXTgV6S7Y7Ymi5BlyLF4JbC0epppa6dFyukUK8eKc/ndCU j1Uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749116111; x=1749720911; 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=O0WVqpx4pzsn2g+f2/hxM0olho/ITNTWEYPLGB0lS6M=; b=I6WlRx6E1lsjHDvc5Hyg/8fJHJAY2GRAi1PtZkO0RU9uANObgAl7ZDNlGUReuo0Ujx dOXABy+W3LpX/uqVeD6rfVMzKnpvU8E/ZrWYHidMLcXRbJ750HmHr2uaHWwucpI2IxLj 7K+xLoBVDW6/FhE+Wg10bFof4W+i+F0lNjicWbLfQW9AN+SbPXvc8FKgIdM6/6QMzUD6 cDpIL6lHujD/++rUyMUkgBB6gQZ1tDDS59ijgrGeYnvSBpVdlPAloWi9DWeZTnSuI3u2 3ThXYgLwvPYkCaGaxOZKPeyvQ7F1hiaivV0BJwSuxQTha5H5j1rPvLZgxJXlSYp91aLy JFCA== X-Gm-Message-State: AOJu0YwMYaLpFQN+IuK8NKaH/20j9ltP+6HwNtg5Dqi/b0pUuwYxKWzs Cpqivk5SYrEjuIARxaK3QHC9LzkWvqt0HVhAmGi7rQKoPmMd/KN4/nShuHjXPyicuUozuu7g4H0 tKbj7MxJriuWQOTl1rCYsPf7Ey7jHztKJXM54 X-Gm-Gg: ASbGnctftIONIB/S3lWe/Pch5vD1H8OgK2cEpkFAgrhmdlZR3hT2uEiZD62EPsiM5Qw eNh7H/VIQR991l9zIUDJQ/NyDWK814YYRErZvrKnBVGzTXe41t4i1ffHzHKF4YUfhFYjxph9RUO qylzRlKVSMRazKSJjuSPtGdLx8sBDgBPTIrLM= X-Google-Smtp-Source: AGHT+IEfX8zNy4VkxJUuwqrPzBGNo+xlDQpZW+a9lfWH1JpQUrCJcxZSdmbJ2LmGbQ1+RVKfoA+1vpnhxBo7kmC70io= X-Received: by 2002:a05:6870:1492:b0:2d5:b914:fe40 with SMTP id 586e51a60fabf-2e9bf412119mr4002461fac.20.1749116100076; Thu, 05 Jun 2025 02:35:00 -0700 (PDT) MIME-Version: 1.0 References: <2cd2cf04ba6ea21678b893dbfebe97bcf82726dc.camel@j-davis.com> In-Reply-To: From: Dominique Devienne Date: Thu, 5 Jun 2025 11:34:48 +0200 X-Gm-Features: AX0GCFv1l5gE8Wk5fXewKFp03Zb0iBeaDIF-uhHQSenptwnYEE9E4gZd06_ru0o Message-ID: Subject: Re: LOCALE C.UTF-8 on EDB Windows v17 server To: Jeff Davis Cc: pgsql-general@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 Thu, Jun 5, 2025 at 11:07=E2=80=AFAM Dominique Devienne wrote: > So... It is possible to have the SAME command on Windows and Linux, > which yields the SAME datcollate and datctype values??? > So far, such a command eludes me, I'm afraid. --DD So I tried to be explicit about lc_collate and lc_ctype too. OK on Linux, KO on Windows... Windows: ddevienne=3D> create database "dd_v168b" encoding 'UTF8' builtin_locale 'C.UTF-8' lc_collate 'C.UTF-8' lc_ctype 'C.UTF-8' ddevienne-> locale_provider 'builtin' template template0; ERROR: invalid LC_COLLATE locale name: "C.UTF-8" HINT: If the locale name is specific to ICU, use ICU_LOCALE. Linux: ddevienne=3D> create database "dd_v168c" encoding 'UTF8' builtin_locale 'C.UTF-8' lc_collate 'C.UTF-8' lc_ctype 'C.UTF-8' ddevienne-> locale_provider 'builtin' template template0; CREATE DATABASE ddevienne=3D> select datlocprovider, datlocale, datcollate, datctype from pg_database where datname =3D 'dd_v168c'; datlocprovider | datlocale | datcollate | datctype ----------------+-----------+------------+---------- b | C.UTF-8 | C.UTF-8 | C.UTF-8 (1 row) AFAIK, C and C.UTF-8 are NOT the same thing, for collations. It is indeed super confusing Jeff. I'm lost. How can I get a datlocprovider | datlocale | datcollate | datctype ----------------+-----------+------------+---------- b | C.UTF-8 | C.UTF-8 | C.UTF-8 database on Windows *AND* Linux? If not possible using the same SQL (but why...), using what SQL?