{"kind": "locale", "major": "18", "item": {"slug": "encoding-gb18030", "name": "GB18030", "name_zh": "", "category": "Client-only encodings", "summary": "National Standard", "aliases": ["gb18030"], "content_hash": "df692ccc7b105a81c36db1205e499f8bdb016e4a72cb2d7ec8af0809ed445e6d", "versions": {"10": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1-4"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "label": "10.23", "major": "10", "channel": "historical", "revision": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9", "source_sha256": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9", "catalog_fingerprint": "691be281b476dde4374d7f805b2bacc2e75bdef40f1e9d3d42e91f97fe95cfd0"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v10.23/postgresql-10.23.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "94a4b2528372458e5662c18d406629266667c437198160a18cdfd2c4a4d6eee9"}, {"url": "/docs/10/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 10 English manual", "sha256": "432ae95551147ca4dfc3eae72f062c61a28b9c6c99a594157cebf005a99118e7"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1-4", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

23.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a023.1 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a023.1.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/CharAliases
BIG5Big FiveTraditional ChineseNoNo1-2WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1-3\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1-3\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1-3\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1-3\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1-3\u00a0
GB18030National StandardChineseNoNo1-4\u00a0
GBKExtended National StandardSimplified ChineseNoNo1-2WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1-3\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1-4\u00a0
SJISShift JISJapaneseNoNo1-2Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1-2\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1-2WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1-4Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n
\n
\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0-127 according to the ASCII standard, while byte values 128-255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/10/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1-4", "encoding_id": "39"}, "comparison_hash": "72ff64999255204293355b34c9f6a3c74147ae050b86ea872a3b9412fa83cd4a"}, "11": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1-4"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "label": "11.22", "major": "11", "channel": "historical", "revision": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0", "source_sha256": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0", "catalog_fingerprint": "8f21f4444b7f68923f4762af0eb7937fa2907026e91249483e79050de012c901"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v11.22/postgresql-11.22.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "2cb7c97d7a0d7278851bbc9c61f467b69c094c72b81740b751108e7892ebe1f0"}, {"url": "/docs/11/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 11 English manual", "sha256": "9a353b738a16f00263532af487704d6d93ba309d249fdc5f57f70c7e8484bbfa"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1-4", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

23.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a023.1 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a023.1.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/CharAliases
BIG5Big FiveTraditional ChineseNoNo1-2WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1-3\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1-3\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1-3\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1-3\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1-3\u00a0
GB18030National StandardChineseNoNo1-4\u00a0
GBKExtended National StandardSimplified ChineseNoNo1-2WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1-3\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1-4\u00a0
SJISShift JISJapaneseNoNo1-2Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1-2\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1-2WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1-4Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0-127 according to the ASCII standard, while byte values 128-255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/11/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1-4", "encoding_id": "39"}, "comparison_hash": "72ff64999255204293355b34c9f6a3c74147ae050b86ea872a3b9412fa83cd4a"}, "12": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1-4"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "label": "12.22", "major": "12", "channel": "historical", "revision": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b", "source_sha256": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b", "catalog_fingerprint": "9f857f4ee4875f9c7de6bfc9df4b757dec8b3a0bb88eadb519c7bd267bd56149"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v12.22/postgresql-12.22.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "8df3c0474782589d3c6f374b5133b1bd14d168086edbc13c6e72e67dd4527a3b"}, {"url": "/docs/12/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 12 English manual", "sha256": "b44f9e8c40984c403f67945e54f0a2566aa08d866159bc0cc93f02707dd19aa3"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1-4", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

23.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a023.1 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a023.1.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/CharAliases
BIG5Big FiveTraditional ChineseNoNo1-2WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1-3\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1-3\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1-3\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1-3\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1-3\u00a0
GB18030National StandardChineseNoNo1-4\u00a0
GBKExtended National StandardSimplified ChineseNoNo1-2WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1-3\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1-4\u00a0
SJISShift JISJapaneseNoNo1-2Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1-2\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1-2WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1-4Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0-127 according to the ASCII standard, while byte values 128-255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/12/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1-4", "encoding_id": "39"}, "comparison_hash": "72ff64999255204293355b34c9f6a3c74147ae050b86ea872a3b9412fa83cd4a"}, "13": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1\u20134"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "label": "13.23", "major": "13", "channel": "historical", "revision": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6", "source_sha256": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6", "catalog_fingerprint": "c7015c845255c9d721c547c8ab9ef37825d332588c9691d982e6906b7d571002"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v13.23/postgresql-13.23.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "6ec3c82726af92b7dec873fa1cdf881eca92a4219787dfad05acb6b10e041fd6"}, {"url": "/docs/13/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 13 English manual", "sha256": "0b6e63bcc2dd6d306e394add733e0691643ca1cdbf25246d32b5c2dbac7e0b0e"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

23.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a023.1 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a023.1.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/\u200bCharAliases
BIG5Big FiveTraditional ChineseNoNo1\u20132WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1\u20133\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1\u20133\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1\u20133\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1\u20133\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1\u20134\u00a0
GB18030National StandardChineseNoNo1\u20134\u00a0
GBKExtended National StandardSimplified ChineseNoNo1\u20132WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1\u20133\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1\u20134\u00a0
SJISShift JISJapaneseNoNo1\u20132Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1\u20132\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1\u20132WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1\u20134Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0\u2013127 according to the ASCII standard, while byte values 128\u2013255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/13/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "comparison_hash": "244c8170e7d2f06ecb2277076292dba0be58db179f601251edd9ca1fea5529f0"}, "14": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1\u20134"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "label": "14.24", "major": "14", "channel": "stable", "revision": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897", "source_sha256": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897", "catalog_fingerprint": "b272e6a82e4c46efda81c3a6a4cdf7de6a83dfff7f02f226a392fbe9acdd3adb"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v14.24/postgresql-14.24.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "a7fa7ed3d558172355f51406097a7bd4f6b473be80f311ef7cda96bf383d8897"}, {"url": "/docs/14/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 14 English manual", "sha256": "51ecfb763cca4365a783cf28b42848c915579b5103d9d6fd530018be23381191"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

24.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a024.1 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a024.1.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/\u200bCharAliases
BIG5Big FiveTraditional ChineseNoNo1\u20132WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1\u20133\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1\u20133\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1\u20133\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1\u20133\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1\u20134\u00a0
GB18030National StandardChineseNoNo1\u20134\u00a0
GBKExtended National StandardSimplified ChineseNoNo1\u20132WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1\u20133\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1\u20134\u00a0
SJISShift JISJapaneseNoNo1\u20132Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1\u20132\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1\u20132WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1\u20134Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0\u2013127 according to the ASCII standard, while byte values 128\u2013255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/14/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "comparison_hash": "244c8170e7d2f06ecb2277076292dba0be58db179f601251edd9ca1fea5529f0"}, "15": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1\u20134"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "label": "15.19", "major": "15", "channel": "stable", "revision": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89", "source_sha256": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89", "catalog_fingerprint": "fefe3c425147a86defada190c9b0663cfe02caa1724f5dede93e46457572252d"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v15.19/postgresql-15.19.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "e1a64a87a46b825b88c082e4518161a47aab53c45694964f8ba1df28f7859f89"}, {"url": "/docs/15/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 15 English manual", "sha256": "0ec9e607540b8a284214d12d8b207d59008e3bfb6f7d4ba8cebcdfd1d2cc0c05"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

24.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a024.1 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a024.1.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/\u200bCharAliases
BIG5Big FiveTraditional ChineseNoNo1\u20132WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1\u20133\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1\u20133\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1\u20133\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1\u20133\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1\u20134\u00a0
GB18030National StandardChineseNoNo1\u20134\u00a0
GBKExtended National StandardSimplified ChineseNoNo1\u20132WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1\u20133\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1\u20134\u00a0
SJISShift JISJapaneseNoNo1\u20132Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1\u20132\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1\u20132WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1\u20134Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0\u2013127 according to the ASCII standard, while byte values 128\u2013255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/15/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "comparison_hash": "244c8170e7d2f06ecb2277076292dba0be58db179f601251edd9ca1fea5529f0"}, "16": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1\u20134"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "label": "16.15", "major": "16", "channel": "stable", "revision": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed", "source_sha256": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed", "catalog_fingerprint": "fa133458dc8f52e15083b4f59b7a582e2e378b608d3ac5c53054df458a374e23"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"}, {"url": "/docs/16/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 16 English manual", "sha256": "073fc9901f5c4d3fdcd5bbb7d78f4b908dd0fc45799c3489cc213c1508de9bb6"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

24.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a024.3 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a024.3.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/\u200bCharAliases
BIG5Big FiveTraditional ChineseNoNo1\u20132WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1\u20133\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1\u20133\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1\u20133\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1\u20133\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1\u20134\u00a0
GB18030National StandardChineseNoNo1\u20134\u00a0
GBKExtended National StandardSimplified ChineseNoNo1\u20132WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1\u20133\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1\u20134\u00a0
SJISShift JISJapaneseNoNo1\u20132Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1\u20132\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1\u20132WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1\u20134Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0\u2013127 according to the ASCII standard, while byte values 128\u2013255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/16/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "comparison_hash": "244c8170e7d2f06ecb2277076292dba0be58db179f601251edd9ca1fea5529f0"}, "17": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1\u20134"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "label": "17.11", "major": "17", "channel": "stable", "revision": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979", "source_sha256": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979", "catalog_fingerprint": "4bbe3ac77becd618478f66aec420a533e9017be356c5c1d51a4b17f0fd497c07"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v17.11/postgresql-17.11.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "dd27f2b3c59e73ed14aa3324901242bf69a032a6347805f274e6260322d42979"}, {"url": "/docs/17/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 17 English manual", "sha256": "0c181f686034a19d30fb9033017d6898958afaa5c1ae8d09e35a9996e806920a"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

23.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a023.3 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a023.3.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/\u200bCharAliases
BIG5Big FiveTraditional ChineseNoNo1\u20132WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1\u20133\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1\u20133\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1\u20133\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1\u20133\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1\u20134\u00a0
GB18030National StandardChineseNoNo1\u20134\u00a0
GBKExtended National StandardSimplified ChineseNoNo1\u20132WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1\u20133\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1\u20134\u00a0
SJISShift JISJapaneseNoNo1\u20132Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1\u20132\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1\u20132WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1\u20134Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0\u2013127 according to the ASCII standard, while byte values 128\u2013255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/17/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "comparison_hash": "244c8170e7d2f06ecb2277076292dba0be58db179f601251edd9ca1fea5529f0"}, "18": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1\u20134"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "label": "18.6", "major": "18", "channel": "stable", "revision": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f", "source_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f", "catalog_fingerprint": "65c93d6048ef30e61023a84f9680fa6a92b1c383b7eb226741170077eb078502"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "/docs/18/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 18 English manual", "sha256": "35b8983bd9f17eae726bed4e59e564ca55e0d6fde5851a25b683b3f9a396acb0"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

23.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a023.3 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a023.3.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/\u200bCharAliases
BIG5Big FiveTraditional ChineseNoNo1\u20132WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1\u20133\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1\u20133\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1\u20133\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1\u20133\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1\u20134\u00a0
GB18030National StandardChineseNoNo1\u20134\u00a0
GBKExtended National StandardSimplified ChineseNoNo1\u20132WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1\u20133\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1\u20134\u00a0
SJISShift JISJapaneseNoNo1\u20132Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1\u20132\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1\u20132WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1\u20134Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0\u2013127 according to the ASCII standard, while byte values 128\u2013255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/18/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "comparison_hash": "244c8170e7d2f06ecb2277076292dba0be58db179f601251edd9ca1fea5529f0"}, "19": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1\u20134"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "label": "19beta4", "major": "19", "channel": "preview", "revision": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86", "source_sha256": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86", "catalog_fingerprint": "62fbf1a3689dbe8bf7e6b3372cfe6fbf867581427b3858a94c8419b77a4d2d1d"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86"}, {"url": "/docs/19/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 19 English manual", "sha256": "5d995c4c21d96cae3d1e329f2e0233cc3c239d184539316408a1b5c060cf9371"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "description": ["National Standard, version 2022"], "manual_html": "
\n
\n
\n
\n

23.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a023.3 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a023.3.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/\u200bCharAliases
BIG5Big FiveTraditional ChineseNoNo1\u20132WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1\u20133\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1\u20133\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1\u20133\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1\u20133\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1\u20134\u00a0
GB18030National Standard, version 2022ChineseNoNo1\u20134\u00a0
GBKExtended National StandardSimplified ChineseNoNo1\u20132WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1\u20133\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
SJISShift JISJapaneseNoNo1\u20132Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1\u20132\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1\u20132WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1\u20134Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0\u2013127 according to the ASCII standard, while byte values 128\u2013255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/19/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "comparison_hash": "244c8170e7d2f06ecb2277076292dba0be58db179f601251edd9ca1fea5529f0"}, "20": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1\u20134"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "label": "20devel", "major": "20", "channel": "devel", "revision": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41", "source_sha256": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41", "catalog_fingerprint": "398fbb9f262264053c02fbf79f88be0a6770c1473faa6ecd5931d6ec41b8258b", "source_snapshot_utc": "26-Sep-2026 20:22"}, "sources": [{"url": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41"}, {"url": "/docs/devel/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 20 English manual", "sha256": "5911c9aeb107e844259cd31679feb381997903d46c26f08516f069566961f272"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "description": ["National Standard, version 2022"], "manual_html": "
\n
\n
\n
\n

23.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a023.3 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a023.3.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/\u200bCharAliases
BIG5Big FiveTraditional ChineseNoNo1\u20132WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1\u20133\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1\u20133\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1\u20133\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1\u20133\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1\u20134\u00a0
GB18030National Standard, version 2022ChineseNoNo1\u20134\u00a0
GBKExtended National StandardSimplified ChineseNoNo1\u20132WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1\u20133\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
SJISShift JISJapaneseNoNo1\u20132Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1\u20132\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1\u20132WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1\u20134Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0\u2013127 according to the ASCII standard, while byte values 128\u2013255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/devel/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "comparison_hash": "244c8170e7d2f06ecb2277076292dba0be58db179f601251edd9ca1fea5529f0"}}}, "snapshot": {"facts": [{"label": "Encoding", "value": "GB18030"}, {"label": "Encoding id", "value": "39"}, {"label": "Language", "value": "Chinese"}, {"label": "Server?", "value": "No"}, {"label": "Icu?", "value": "No"}, {"label": "Bytes/char", "value": "1\u20134"}], "tables": [], "aliases": ["gb18030"], "related": [], "release": {"ref": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "label": "18.6", "major": "18", "channel": "stable", "revision": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f", "source_sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f", "catalog_fingerprint": "65c93d6048ef30e61023a84f9680fa6a92b1c383b7eb226741170077eb078502"}, "sources": [{"url": "https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2", "label": "Matching PostgreSQL source archive", "sha256": "555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}, {"url": "/docs/18/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "path": "multibyte.html", "label": "PostgreSQL 18 English manual", "sha256": "35b8983bd9f17eae726bed4e59e564ca55e0d6fde5851a25b683b3f9a396acb0"}], "sections": [], "signature": "", "attributes": {"ICU?": "No", "Server?": "No", "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "description": ["National Standard"], "manual_html": "
\n
\n
\n
\n

23.3.1.\u00a0Supported Character Sets

\n
\n
\n
\n

Table\u00a023.3 shows the character sets available for use in PostgreSQL.

\n
\n

Table\u00a023.3.\u00a0PostgreSQL Character Sets

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescriptionLanguageServer?ICU?Bytes/\u200bCharAliases
BIG5Big FiveTraditional ChineseNoNo1\u20132WIN950, Windows950
EUC_CNExtended UNIX Code-CNSimplified ChineseYesYes1\u20133\u00a0
EUC_JPExtended UNIX Code-JPJapaneseYesYes1\u20133\u00a0
EUC_JIS_2004Extended UNIX Code-JP, JIS X 0213JapaneseYesNo1\u20133\u00a0
EUC_KRExtended UNIX Code-KRKoreanYesYes1\u20133\u00a0
EUC_TWExtended UNIX Code-TWTraditional Chinese, TaiwaneseYesYes1\u20134\u00a0
GB18030National StandardChineseNoNo1\u20134\u00a0
GBKExtended National StandardSimplified ChineseNoNo1\u20132WIN936, Windows936
ISO_8859_5ISO 8859-5, ECMA 113Latin/CyrillicYesYes1\u00a0
ISO_8859_6ISO 8859-6, ECMA 114Latin/ArabicYesYes1\u00a0
ISO_8859_7ISO 8859-7, ECMA 118Latin/GreekYesYes1\u00a0
ISO_8859_8ISO 8859-8, ECMA 121Latin/HebrewYesYes1\u00a0
JOHABJOHABKorean (Hangul)NoNo1\u20133\u00a0
KOI8RKOI8-RCyrillic (Russian)YesYes1KOI8
KOI8UKOI8-UCyrillic (Ukrainian)YesYes1\u00a0
LATIN1ISO 8859-1, ECMA 94Western EuropeanYesYes1ISO88591
LATIN2ISO 8859-2, ECMA 94Central EuropeanYesYes1ISO88592
LATIN3ISO 8859-3, ECMA 94South EuropeanYesYes1ISO88593
LATIN4ISO 8859-4, ECMA 94North EuropeanYesYes1ISO88594
LATIN5ISO 8859-9, ECMA 128TurkishYesYes1ISO88599
LATIN6ISO 8859-10, ECMA 144NordicYesYes1ISO885910
LATIN7ISO 8859-13BalticYesYes1ISO885913
LATIN8ISO 8859-14CelticYesYes1ISO885914
LATIN9ISO 8859-15LATIN1 with Euro and accentsYesYes1ISO885915
LATIN10ISO 8859-16, ASRO SR 14111RomanianYesNo1ISO885916
MULE_INTERNALMule internal codeMultilingual EmacsYesNo1\u20134\u00a0
SJISShift JISJapaneseNoNo1\u20132Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004Shift JIS, JIS X 0213JapaneseNoNo1\u20132\u00a0
SQL_ASCIIunspecified (see text)anyYesNo1\u00a0
UHCUnified Hangul CodeKoreanNoNo1\u20132WIN949, Windows949
UTF8Unicode, 8-bitallYesYes1\u20134Unicode
WIN866Windows CP866CyrillicYesYes1ALT
WIN874Windows CP874ThaiYesNo1\u00a0
WIN1250Windows CP1250Central EuropeanYesYes1\u00a0
WIN1251Windows CP1251CyrillicYesYes1WIN
WIN1252Windows CP1252Western EuropeanYesYes1\u00a0
WIN1253Windows CP1253GreekYesYes1\u00a0
WIN1254Windows CP1254TurkishYesYes1\u00a0
WIN1255Windows CP1255HebrewYesYes1\u00a0
WIN1256Windows CP1256ArabicYesYes1\u00a0
WIN1257Windows CP1257BalticYesYes1\u00a0
WIN1258Windows CP1258VietnameseYesYes1ABC, TCVN, TCVN5712, VSCII
\n
\n

\n

Not all client APIs support all the listed character sets. For example, the PostgreSQL JDBC driver does not support MULE_INTERNAL, LATIN6, LATIN8, and LATIN10.

\n

The SQL_ASCII setting behaves considerably differently from the other settings. When the server character set is SQL_ASCII, the server interprets byte values 0\u2013127 according to the ASCII standard, while byte values 128\u2013255 are taken as uninterpreted characters. No encoding conversion will be done when the setting is SQL_ASCII. Thus, this setting is not so much a declaration that a specific encoding is in use, as a declaration of ignorance about the encoding. In most cases, if you are working with any non-ASCII data, it is unwise to use the SQL_ASCII setting because PostgreSQL will be unable to help you by converting or validating non-ASCII characters.

\n
", "manual_path": "/docs/18/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED", "comparison_data": {"ICU?": "No", "Server?": "No", "aliases": ["gb18030"], "Language": "Chinese", "encoding": "GB18030", "Bytes/Char": "1\u20134", "encoding_id": "39"}, "comparison_hash": "244c8170e7d2f06ecb2277076292dba0be58db179f601251edd9ca1fea5529f0"}, "comparison": {"left": "12", "right": "13", "status": "changed", "diff": "--- PostgreSQL 12\n+++ PostgreSQL 13\n@@ -1,5 +1,5 @@\n {\n- \"Bytes/Char\": \"1-4\",\n+ \"Bytes/Char\": \"1\u20134\",\n \"ICU?\": \"No\",\n \"Language\": \"Chinese\",\n \"Server?\": \"No\","}}