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.96) (envelope-from ) id 1wJe0a-0005wD-2l for pgsql-general@arkaria.postgresql.org; Sun, 03 May 2026 21:05:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wJe0Z-004hJM-1j for pgsql-general@arkaria.postgresql.org; Sun, 03 May 2026 21:05:47 +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.96) (envelope-from ) id 1wJe0Z-004hJE-0I for pgsql-general@lists.postgresql.org; Sun, 03 May 2026 21:05:47 +0000 Received: from mail-oi1-x234.google.com ([2607:f8b0:4864:20::234]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wJe0W-000000002JF-3Vgm for pgsql-general@lists.postgresql.org; Sun, 03 May 2026 21:05:46 +0000 Received: by mail-oi1-x234.google.com with SMTP id 5614622812f47-47c6f914617so1205409b6e.1 for ; Sun, 03 May 2026 14:05:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1777842344; cv=none; d=google.com; s=arc-20240605; b=lVAA/TEPl3DhiGa+qimlRPj0mHgyJGTl1klg8pEe6OhBwuey0d1Cs1a7ur+E9c/+vI Vq7DbGa9OgFwN2Mze9YkZNfOjui6gmJa8Nj+ABiSnoxgLxB019iaSrW+Ns33YdAV4r7Z XPQP2u5F52BdWoYkxOnr3xIiv4AhhcThK/8/h+gPzBbEoNLS8bSICPDeRhbHN94jqsd5 y75+KLHoOHSkGtm13x/dgPG+LyJHVqf7Hxx8dUzzeMuTLqkSwBus/sezV8U0weDk/J0y gZr1Q6TdIzt1JPeY3G2Vr1d7Fx3vgzLRyx1TyKfHykqLD+5fop24gyhT9tiEcl2lP1G2 IjbQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=fhQ72bKvKZQVIDqiLdhSLs+II+Wq6A+ZnMSHKS1K6Mo=; fh=2DoGC78b0mi8uZ4UY+9ocPF86GSVzeaJWqou/x907js=; b=AwJ/91uG6yA9/bFwqjZH+o3qUq3ZDobma/es2zNxv+mzcwR98eqswFIxbNrD3xFn/w SURaEYkiFYKmlYVDLN+Nrvu88Qn7UkCw8r5KEG7f2NB5lM9gMeyfK5sRmCLqqkY7LQaF ioZqNIJcFtt0nZZrQReLro+QDL58QX0HC50Pd0ztPxV80uEXkRYfgXUt0DTyT8VJ828m hbX3AuEuqfN6BE6Wy2gYIIlLIjXZr1r7cFB1tORPmy6+ImYjmetCDvmNogleYvPBI7X1 pLFL/zC/+AbkM0S4DAvq5P/kGpCs+nWCGgX4qvDIsWw8hCFqqv51nBvVVtWKZ/1Zr2lN q9Ew==; darn=lists.postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1777842344; x=1778447144; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=fhQ72bKvKZQVIDqiLdhSLs+II+Wq6A+ZnMSHKS1K6Mo=; b=h8yFLqTt6QPFmKdjR2TeYQbMVHB7L1oYQN9n4uvSRuWp28AtGjDtMSriB2RWcbmA4A wC8nCh6YQCQDgYW009vuIW7Z9TyMVm/XvfWbiO8MVJ473wCWKraCVEucWWKj4cLgGmsj ZLkbcjRnEE23kuowS+XXxR9zrAev585P/JSb/99iM2Y48NmPVQmgm29brodtk9zVwCSe X0tR5YTGqdKqhywBUxfzfaKVJKXbM41mcwiSlJri0Ot7PiWaFMxzNJpcMiCvQWUn8A1z IxGfsNW8Z/Kb3RKyWvpoTczP0BXQSi+JyLB6G7IcjyXllA4T98EaQhvJ3B6CdgXaPQGk eZFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777842344; x=1778447144; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fhQ72bKvKZQVIDqiLdhSLs+II+Wq6A+ZnMSHKS1K6Mo=; b=FGUEfweDejl4plUXL8JWX7nUlpZlkEZzXdIT+AAO9KrcOXVOuAi3EyMdKb4b+SIZyX MvGZIClYx2l5iWCcByJnvOmHYeWgvgrXrpb/nkZOYHE+nKLlLtQR62gkC+vxxROt+fIQ JWkOOH1ajZX0+ELw7y4fcTT2xGnRI+E2uxWjHDkzxCe+bzd4Xb2uSFB9+OJXzRhbqY3C e/ubrUMbADEqEiM+OhTfJjKLaZZQ0AfuFGV3J7MEMHKNfrC4zWiK84jC+prRrLb81Clf BhxiNpr7KzVUdTlPA5+nW6KTVlABDbrVhsny1uCkY0VJYABvS0x155TnVaGR7KSxyFbM ieJg== X-Gm-Message-State: AOJu0YzDVgLmTE0l/ey7ZLnQ7UKwxpZc0t6EMIULubnR8ifO07YVYUFD Rz1wnVDVr2u8X6FfpQw4W6yf0fProVEhrE1tQtx0p2Xf+euMe3FW1WizOZ4IkyeuvkBxf1n+HR1 8ef3XxWd42KLQBswNL52PtH6m6DDEv60qAQ== X-Gm-Gg: AeBDiesz3yuN1fdJcu9+Qwrvrh4xcw0pI1yAXMJck/FglAUcXiffHRjDVWKxlAMMk4B HrQ/nWVjPE+06Ko5b4Nb+yWzwN6VpfM4hyGy720osQGFmwcpkmsjG0PEeu4GhfJD2/VqxT/TZAi yP0QGkqQxIoBLC+9zdZVx/fUr2JCVMbaUH3/WpE2Q5xu4kLqxnIVycjCLvPVjOSQOGcAH+dyZuA 3BzvSeEnRtyB8kDWlYdNH9MLyWui1bnOmBtTPm8nr/zXAMnu93xVnVFXHGXTxougCA40vJpiMTa 3Snw6AxhtVQ9/Qn5rsM= X-Received: by 2002:a05:6808:1a01:b0:471:f036:791f with SMTP id 5614622812f47-47c8923ae37mr3378629b6e.30.1777842344472; Sun, 03 May 2026 14:05:44 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Sun, 3 May 2026 17:05:32 -0400 X-Gm-Features: AVHnY4JtMM_N3PkQyNhe5ZEQ5PHhVcEQ5z_P1cowshC6Wx-9dpHgyMB-Zw_6-bg Message-ID: Subject: Re: Choosing default collation/ctype To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000068b1ea0650f02d74" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000068b1ea0650f02d74 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, May 3, 2026 at 4:52=E2=80=AFPM Igor Korot wrot= e: > Hi, > > On Sun, May 3, 2026 at 3:09=E2=80=AFPM Ron Johnson > wrote: > > > > On Sun, May 3, 2026 at 3:52=E2=80=AFPM Igor Korot = wrote: > >> > >> Hi, ALL, > >> In the CREATE DATABASE statement I can use encoding/collation/ctype. > >> > >> I can retrieve the encoding list with: > >> > >> [code] > >> SELECT pg_encoding_to_char( conforencoding ) AS name FROM pg_conversio= n > >> [/code] > >> > >> And then I can get a list of collations/ctypes with: > >> > >> [code] > >> SELECT collname, collencoding, collprovider collctype FROM pg_collatio= n > >> [/code] > >> > >> And then add a logic in my UI to switch collations/ctypes based on > encoding. > >> > >> However, what I wonder is: > >> > >> Is there a way to select a default collation/ctype for a specific > encoding? > >> > >> Or maybe I'm overthinking it and I should let the user choose and if > >> nothing - just keep those 2 as "Default" and let the server pick it > >> up. However it will be weird, especially from me as a user POV. > > > > > > You know your data, not us. The first question I'd try to is "how much > client text data is not compatible with bog-standard UTF8?" > > I don't. > Just trying to create a generic tool to use for people everywhere... > Then choose UTF8. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --00000000000068b1ea0650f02d74 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, May 3, 2026 at 4:52=E2=80=AFPM Ig= or Korot <ikorot01@gmail.com&g= t; wrote:
Hi,

On Sun, May 3, 2026 at 3:09=E2=80=AFPM Ron Johnson <ronljohnsonjr@gmail.com> wr= ote:
>
> On Sun, May 3, 2026 at 3:52=E2=80=AFPM Igor Korot <ikorot01@gmail.com> wrote: >>
>> Hi, ALL,
>> In the CREATE DATABASE statement I can use encoding/collation/ctyp= e.
>>
>> I can retrieve the encoding list with:
>>
>> [code]
>> SELECT pg_encoding_to_char( conforencoding ) AS name FROM pg_conve= rsion
>> [/code]
>>
>> And then I can get a list of collations/ctypes with:
>>
>> [code]
>> SELECT collname, collencoding, collprovider collctype FROM pg_coll= ation
>> [/code]
>>
>> And then add a logic in my UI to switch collations/ctypes based on= encoding.
>>
>> However, what I wonder is:
>>
>> Is there a way to select a default collation/ctype for a specific = encoding?
>>
>> Or maybe I'm overthinking it and I should let the user choose = and if
>> nothing - just keep those 2 as "Default" and let the ser= ver pick it
>> up. However it will be weird, especially from me as a user POV. >
>
> You know your data, not us.=C2=A0 The first question I'd try to is= "how much client text data is not compatible with bog-standard UTF8?&= quot;

I don't.
Just trying to create a generic tool to use for people everywhere...
=C2=A0
Then choose UTF8.

--
Death to <Redacted>, and butte= r sauce.
Don't boil me, I'm still alive.
<Redac= ted> lobster!
--00000000000068b1ea0650f02d74--