Re: List of encodings

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: List of encodings
Date: 2026-04-20 01:31:43
Message-ID: CANzqJaBRRq5T-3VJc5fzGSOotAW8eXg1cvh0XwoRc4akO+mamg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Apr 19, 2026 at 9:13 PM Igor Korot <ikorot01(at)gmail(dot)com> wrote:

> [snip]
> >
> > In your setup all the installed encoding conversion functions are also
> > the default for those conversions. It is possible to create/install a
> > conversion function that is not the default.
>
> So, let's say I chose "BIG5"".
>
> As stated the table contains:
>
> big5_to_utf8 | BIG5 | t
> big5_to_euc_tw | BIG5 | t
> big5_to_mic | BIG5 | t
>
> Since all 3 are default character sets, which one would be chosen?
> (in the context of CREATE DATABASE)
>

Does CREATE DATABASE *convert text*? (I think you might be
misunderstanding the purpose of the pg_conversion table.)

Wouldn't it only *convert* text when a client is inserting text of encoding
X into a table with encoding Y?

ISTM that pg_conversion says whether PG knows how to convert from X to Y,
not the encoding scheme you defined when creating the db.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2026-04-20 01:49:30 Re: List of encodings
Previous Message Igor Korot 2026-04-20 01:13:29 Re: List of encodings