From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Questionabl description in datatype.sgml |
Date: | 2016-06-18 12:04:17 |
Message-ID: | 20160618.210417.343199294611427151.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In "8.13.2. Encoding Handling"
<para>
When using binary mode to pass query parameters to the server
and query results back to the client, no character set conversion
is performed, so the situation is different. In this case, an
encoding declaration in the XML data will be observed, and if it
is absent, the data will be assumed to be in UTF-8 (as required by
the XML standard; note that PostgreSQL does not support UTF-16).
On output, data will have an encoding declaration
specifying the client encoding, unless the client encoding is
UTF-8, in which case it will be omitted.
</para>
In the first sentence shouldn't "no character set conversion" be "no
encoding conversion"? PostgreSQL is doing client/server encoding
conversion, rather than character set conversion.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-06-18 12:08:52 | Re: forcing a rebuild of the visibility map |
Previous Message | Amit Kapila | 2016-06-18 04:57:44 | Re: pgsql: Try again to fix the way the scanjoin_target is used with partia |