↑↓ select ↵ open ⌫ change scope Open full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

Wiki / Collations & Encodings / Server encodings

EUC_KR

Extended UNIX Code-KR

Reading PostgreSQL 18.6.

Description

Extended UNIX Code-KR

Encoding
EUC_KR
Encoding id
3
Language
Korean
Server?
Yes
Icu?
Yes
Bytes/char
1–3

Manual definition

23.3.1. Supported Character Sets

Table 23.3 shows the character sets available for use in PostgreSQL.

Table 23.3. PostgreSQL Character Sets

Name Description Language Server? ICU? Bytes/​Char Aliases
BIG5 Big Five Traditional Chinese No No 1–2 WIN950, Windows950
EUC_CN Extended UNIX Code-CN Simplified Chinese Yes Yes 1–3  
EUC_JP Extended UNIX Code-JP Japanese Yes Yes 1–3  
EUC_JIS_2004 Extended UNIX Code-JP, JIS X 0213 Japanese Yes No 1–3  
EUC_KR Extended UNIX Code-KR Korean Yes Yes 1–3  
EUC_TW Extended UNIX Code-TW Traditional Chinese, Taiwanese Yes Yes 1–4  
GB18030 National Standard Chinese No No 1–4  
GBK Extended National Standard Simplified Chinese No No 1–2 WIN936, Windows936
ISO_8859_5 ISO 8859-5, ECMA 113 Latin/Cyrillic Yes Yes 1  
ISO_8859_6 ISO 8859-6, ECMA 114 Latin/Arabic Yes Yes 1  
ISO_8859_7 ISO 8859-7, ECMA 118 Latin/Greek Yes Yes 1  
ISO_8859_8 ISO 8859-8, ECMA 121 Latin/Hebrew Yes Yes 1  
JOHAB JOHAB Korean (Hangul) No No 1–3  
KOI8R KOI8-R Cyrillic (Russian) Yes Yes 1 KOI8
KOI8U KOI8-U Cyrillic (Ukrainian) Yes Yes 1  
LATIN1 ISO 8859-1, ECMA 94 Western European Yes Yes 1 ISO88591
LATIN2 ISO 8859-2, ECMA 94 Central European Yes Yes 1 ISO88592
LATIN3 ISO 8859-3, ECMA 94 South European Yes Yes 1 ISO88593
LATIN4 ISO 8859-4, ECMA 94 North European Yes Yes 1 ISO88594
LATIN5 ISO 8859-9, ECMA 128 Turkish Yes Yes 1 ISO88599
LATIN6 ISO 8859-10, ECMA 144 Nordic Yes Yes 1 ISO885910
LATIN7 ISO 8859-13 Baltic Yes Yes 1 ISO885913
LATIN8 ISO 8859-14 Celtic Yes Yes 1 ISO885914
LATIN9 ISO 8859-15 LATIN1 with Euro and accents Yes Yes 1 ISO885915
LATIN10 ISO 8859-16, ASRO SR 14111 Romanian Yes No 1 ISO885916
MULE_INTERNAL Mule internal code Multilingual Emacs Yes No 1–4  
SJIS Shift JIS Japanese No No 1–2 Mskanji, ShiftJIS, WIN932, Windows932
SHIFT_JIS_2004 Shift JIS, JIS X 0213 Japanese No No 1–2  
SQL_ASCII unspecified (see text) any Yes No 1  
UHC Unified Hangul Code Korean No No 1–2 WIN949, Windows949
UTF8 Unicode, 8-bit all Yes Yes 1–4 Unicode
WIN866 Windows CP866 Cyrillic Yes Yes 1 ALT
WIN874 Windows CP874 Thai Yes No 1  
WIN1250 Windows CP1250 Central European Yes Yes 1  
WIN1251 Windows CP1251 Cyrillic Yes Yes 1 WIN
WIN1252 Windows CP1252 Western European Yes Yes 1  
WIN1253 Windows CP1253 Greek Yes Yes 1  
WIN1254 Windows CP1254 Turkish Yes Yes 1  
WIN1255 Windows CP1255 Hebrew Yes Yes 1  
WIN1256 Windows CP1256 Arabic Yes Yes 1  
WIN1257 Windows CP1257 Baltic Yes Yes 1  
WIN1258 Windows CP1258 Vietnamese Yes Yes 1 ABC, TCVN, TCVN5712, VSCII

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.

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.

Documentation and source

Source build
Version
18.6
Build
https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2
Source fingerprint
555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f

Compare versions

PostgreSQL 17 → 18: unchanged.

Compares recorded interfaces and attributes. Source fingerprints and build metadata are excluded; an absent sample is not proof of the introduction or removal release.

Related entries

Export JSON · Back to Collations & Encodings · Recorded in PostgreSQL 10 through 20; the first sample is not necessarily its introduction.