1
0
mirror of https://github.com/postgres/postgres.git synced 2025-08-27 07:42:10 +03:00

doc: Fix descriptions related to the handling of non-ASCII characters

Since 45b1a67a0f, non-printable ASCII characters do not show up in
various configuration paths as question marks, but as hexadecimal
escapes.  The documentation was not updated to reflect that.

Author: Hayato Kuroda
Reviewed-by: Jian He, Tom Lane, Karl O. Pinc, Peter Smith
Discussion: https://postgr.es/m/TYAPR01MB586631D0961BF9C44893FAB1F523A@TYAPR01MB5866.jpnprd01.prod.outlook.com
Backpatch-through: 16
This commit is contained in:
Michael Paquier
2023-09-29 10:34:04 +09:00
parent 714780dcdd
commit 3ef18a90bd
2 changed files with 12 additions and 9 deletions

View File

@@ -1067,9 +1067,9 @@ postgres=# SELECT postgres_fdw_disconnect_all();
of any length and contain even non-ASCII characters. However when
it's passed to and used as <varname>application_name</varname>
in a foreign server, note that it will be truncated to less than
<symbol>NAMEDATALEN</symbol> characters and anything other than
printable ASCII characters will be replaced with question
marks (<literal>?</literal>).
<symbol>NAMEDATALEN</symbol> characters.
Anything other than printable ASCII characters are replaced with <link
linkend="sql-syntax-strings-escape">C-style hexadecimal escapes</link>.
See <xref linkend="guc-application-name"/> for details.
</para>