Re: List of encodings
Adrian Klaver <adrian.klaver@aklaver.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Igor Korot <ikorot01@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
"pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2026-04-20T00:53:21Z
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.klaver@aklaver.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.klaver@aklaver.com