From: Tom Lane <tgl@sss.pgh.pa.us>
To: Igor Korot <ikorot01@gmail.com>
cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: List of encodings
In-reply-to: <CA+FnnTxFMiA+KMfypfGyY43G2kSx6-t5A351snUMmWC-2Lxvaw@mail.gmail.com>
References: <CA+FnnTxFMiA+KMfypfGyY43G2kSx6-t5A351snUMmWC-2Lxvaw@mail.gmail.com>
Comments: In-reply-to Igor Korot <ikorot01@gmail.com>
	message dated "Sat, 18 Apr 2026 01:46:16 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3432385.1776524911.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 18 Apr 2026 11:08:31 -0400
Message-ID: <3432386.1776524911@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3432386.1776524911%40sss.pgh.pa.us>
Precedence: bulk

Igor Korot <ikorot01@gmail.com> writes:
> Does the list shown in
> https://www.postgresql.org/docs/current/multibyte.html#MULTIBYTE-CHARSET=
-SUPPORTED
> stored somewhere in INFORMATION_SCHEMA?

No, the SQL standard doesn't specify any such view.

You could try

# select n, pg_encoding_to_char(n) from generate_series(0,50) n;
 n  | pg_encoding_to_char =

----+---------------------
  0 | SQL_ASCII
  1 | EUC_JP
  2 | EUC_CN
  3 | EUC_KR
  4 | EUC_TW
  5 | EUC_JIS_2004
  6 | UTF8
  ...

			regards, tom lane