From 3ef18a90bdeaeb7895b16431b0bb0023265c1df4 Mon Sep 17 00:00:00 2001
From: Michael Paquier
Date: Fri, 29 Sep 2023 10:34:04 +0900
Subject: doc: Fix descriptions related to the handling of non-ASCII characters
Since 45b1a67a0fcb, 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
---
doc/src/sgml/postgres-fdw.sgml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
(limited to 'doc/src/sgml/postgres-fdw.sgml')
diff --git a/doc/src/sgml/postgres-fdw.sgml b/doc/src/sgml/postgres-fdw.sgml
index 5062d712e74..c177fd41bcb 100644
--- a/doc/src/sgml/postgres-fdw.sgml
+++ b/doc/src/sgml/postgres-fdw.sgml
@@ -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 application_name
in a foreign server, note that it will be truncated to less than
- NAMEDATALEN characters and anything other than
- printable ASCII characters will be replaced with question
- marks (?).
+ NAMEDATALEN characters.
+ Anything other than printable ASCII characters are replaced with C-style hexadecimal escapes.
See for details.
--
cgit v1.2.3