Re: List of encodings

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Igor Korot <ikorot01(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: List of encodings
Date: 2026-04-20 00:53:21
Message-ID: 5f263a8a-9c30-4118-b410-6e25eafde156@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 4/19/26 5:19 PM, Igor Korot wrote:
> Hi, Adrian,
>
> On Sun, Apr 19, 2026 at 4:21 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:

>>> What I noticed is that all encodings are default, as they all have 't'
>>> in the last column.
>>>
>>> It's a little confusing...
>>
>> Not if you read the docs:
>>
>> https://www.postgresql.org/docs/current/catalog-pg-conversion.html
>>
>> "The catalog pg_conversion describes encoding conversion functions. See
>> CREATE CONVERSION for more information."
>>
>> https://www.postgresql.org/docs/current/sql-createconversion.html
>>
>> "Conversions that are marked DEFAULT can be used for automatic encoding
>> conversion between client and server. To support that usage, two
>> conversions, from encoding A to B and from encoding B to A, must be
>> defined."
>
> From the https://www.postgresql.org/docs/current/catalog-pg-conversion.html:
>
> [quote]
>
> condefault bool
>
> True if this is the default conversion
> [/quote]
>
> So, what info do I trust?

Both.

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.

>
> Thank you.
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Igor Korot 2026-04-20 00:55:37 Re: List of encodings
Previous Message David G. Johnston 2026-04-20 00:41:22 Re: List of encodings