| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pandora <yeyukui(at)qq(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: whether I can add a new encoding? |
| Date: | 2023-09-21 15:29:27 |
| Message-ID: | 704880.1695310167@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"=?ISO-8859-1?B?UGFuZG9yYQ==?=" <yeyukui(at)qq(dot)com> writes:
> The pg_wchar.h file comments "We must avoid renumbering any backend encoding until libpq's major version number is increased beyond 5", Can I add a new server-side encoding, GBK18030, and place it after PG_KOI8U in PG10.6?
What is GBK18030? If it's related to either GBK or GB18030,
then it'd be unsafe to use as a server encoding because it's not a
strict ASCII superset (that is, it has multibyte characters in
which not all bytes have the high bit set). The lack of room for
a new server encoding in the pg_enc enum has seemed like a mostly
hypothetical problem because of that restriction.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dominique Devienne | 2023-09-21 16:42:38 | How to fork pg_dump or psql w/o leaking secrets? |
| Previous Message | Tatsuo Ishii | 2023-09-21 11:50:33 | Re: whether I can add a new encoding? |