MIME-Version: 1.0
References: <CA+FnnTyJDvLijfizguNahiRO1LMHR4t9=_9-aO8P18cDZ6RRGA@mail.gmail.com>
In-Reply-To: <CA+FnnTyJDvLijfizguNahiRO1LMHR4t9=_9-aO8P18cDZ6RRGA@mail.gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Sun, 3 May 2026 16:09:14 -0400
Message-ID: <CANzqJaB=zwoYT_rBwUX8q4VyqQBGWyjvAiW=UAJZ0+eh7HU0Zg@mail.gmail.com>
Subject: Re: Choosing default collation/ctype
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000fd7d3b0650ef634c"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaB%3DzwoYT_rBwUX8q4VyqQBGWyjvAiW%3DUAJZ0%2Beh7HU0Zg%40mail.gmail.com>
Precedence: bulk

--000000000000fd7d3b0650ef634c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, May 3, 2026 at 3:52=E2=80=AFPM Igor Korot <ikorot01@gmail.com> wrot=
e:

> 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_conversion
> [/code]
>
> And then I can get a list of collations/ctypes with:
>
> [code]
> SELECT collname, collencoding, collprovider collctype FROM pg_collation
> [/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 encodin=
g?
>
> 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?"

--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

--000000000000fd7d3b0650ef634c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sun, May 3, 2026 at 3:52=E2=80=AFPM Ig=
or Korot &lt;<a href=3D"mailto:ikorot01@gmail.com">ikorot01@gmail.com</a>&g=
t; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">Hi, ALL,<br>
In the CREATE DATABASE statement I can use encoding/collation/ctype.<br>
<br>
I can retrieve the encoding list with:<br>
<br>
[code]<br>
SELECT pg_encoding_to_char( conforencoding ) AS name FROM pg_conversion<br>
[/code]<br>
<br>
And then I can get a list of collations/ctypes with:<br>
<br>
[code]<br>
SELECT collname, collencoding, collprovider collctype FROM pg_collation<br>
[/code]<br>
<br>
And then add a logic in my UI to switch collations/ctypes based on encoding=
.<br>
<br>
However, what I wonder is:<br>
<br>
Is there a way to select a default collation/ctype for a specific encoding?=
<br>
<br>
Or maybe I&#39;m overthinking it and I should let the user choose and if<br=
>
nothing - just keep those 2 as &quot;Default&quot; and let the server pick =
it<br>
up. However it will be weird, especially from me as a user POV.<br></blockq=
uote><div><br></div><div>You know your data, not us.=C2=A0 The first questi=
on I&#39;d try to is &quot;how much client text data is not compatible with=
 bog-standard UTF8?&quot;</div></div><div><br></div><span class=3D"gmail_si=
gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><d=
iv dir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<div>Don&#39;t b=
oil me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lobster!</div></=
div></div></div></div></div>

--000000000000fd7d3b0650ef634c--