From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | lars(at)greiz-reinsdorf(dot)de |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Fix docs to JOHAB encoding on server side |
Date: | 2018-09-01 19:04:21 |
Message-ID: | 8473.1535828661@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Lars Kanis <lars(at)greiz-reinsdorf(dot)de> writes:
> The current documentation is inconsistent about the JOHAB character encoding on server side. While the first table says that it is not possible to use JOHAB on server side, it is still listed in table 23.2 as a server character set:
> https://www.postgresql.org/docs/devel/static/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED
Hm, yeah. Probably this is because JOHAB was first installed as being
a server-allowed encoding, and it was only later we realized that wasn't
OK. This table must've been missed while changing it.
Cross-checking the other entries, I notice SHIFT_JIS_2004 is also not
listed in that table ... we've been a little sloppy there.
Thanks for noticing!
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-09-01 19:32:10 | Re: pg_verify_checksums and -fno-strict-aliasing |
Previous Message | Thomas Munro | 2018-09-01 19:04:19 | Re: [HACKERS] PATCH: Keep one postmaster monitoring pipe per process |