public inbox for [email protected]  

help / color / mirror / Atom feed

List of encodings
3+ messages / 3 participants
[nested] [flat]

* List of encodings
@ 2026-04-18 06:46  Igor Korot <[email protected]>
  0 siblings, 2 replies; 3+ messages in thread

From: Igor Korot @ 2026-04-18 06:46 UTC (permalink / raw)
  To: pgsql-generallists.postgresql.org <[email protected]>

Hi, ALL,
Does the list shown in
https://www.postgresql.org/docs/current/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED
stored somewhere in INFORMATION_SCHEMA?

Or is it hard coded inside the PostgreSQL codebase?

Thank you.






^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: List of encodings
@ 2026-04-18 07:19  David G. Johnston <[email protected]>
  parent: Igor Korot <[email protected]>
  1 sibling, 0 replies; 3+ messages in thread

From: David G. Johnston @ 2026-04-18 07:19 UTC (permalink / raw)
  To: Igor Korot <[email protected]>; +Cc: pgsql-generallists.postgresql.org <[email protected]>

On Friday, April 17, 2026, Igor Korot <[email protected]> wrote:

> Hi, ALL,
> Does the list shown in
> https://www.postgresql.org/docs/current/multibyte.html#
> MULTIBYTE-CHARSET-SUPPORTED
> stored somewhere in INFORMATION_SCHEMA?


This wouldn’t be under the purview of information schema.  You can find
pg-specific pieces though:

https://www.postgresql.org/docs/current/catalog-pg-conversion.html

Note the function used to convert ids to names.


>
> Or is it hard coded inside the PostgreSQL codebase?
>

 Yes.  Doesn’t preclude exposing it via SQL but we don’t do so directly.

David J.


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: List of encodings
@ 2026-04-18 15:08  Tom Lane <[email protected]>
  parent: Igor Korot <[email protected]>
  1 sibling, 0 replies; 3+ messages in thread

From: Tom Lane @ 2026-04-18 15:08 UTC (permalink / raw)
  To: Igor Korot <[email protected]>; +Cc: pgsql-generallists.postgresql.org <[email protected]>

Igor Korot <[email protected]> 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






^ permalink  raw  reply  [nested|flat] 3+ messages in thread

end of thread, other threads:[~2026-04-18 15:08 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-04-18 06:46 List of encodings Igor Korot <[email protected]>
2026-04-18 07:19 ` David G. Johnston <[email protected]>
2026-04-18 15:08 ` Tom Lane <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox