Add hint for "invalid byte sequence for encoding" error message,

suggesting review of client_encoding.

diff --git a/src/backend/utils/mb/wchar.c b/src/backend/utils/mb/wchar.c
index 4e40bc60f1dbc82c6fd82e7c99885797213807d9..5635b7320d6949fc2eeb1b24424e29c9695286ee 100644 (file)
--- a/src/backend/utils/mb/wchar.c
+++ b/src/backend/utils/mb/wchar.c
@@ -1,7 +1,7 @@
 /*
  * conversion functions between pg_wchar and multibyte streams.
  * Tatsuo Ishii
- * $PostgreSQL: pgsql/src/backend/utils/mb/wchar.c,v 1.47.2.2 2006/05/21 20:05:48 tgl Exp $
+ * $PostgreSQL: pgsql/src/backend/utils/mb/wchar.c,v 1.47.2.3 2006/08/22 03:38:13 momjian Exp $
  *
  * WIN1250 client encoding updated by Pavel Behal
  *
@@ -1325,7 +1325,10 @@ report_invalid_encoding(int encoding, const char *mbstr, int len)
                        (errcode(ERRCODE_CHARACTER_NOT_IN_REPERTOIRE),
                         errmsg("invalid byte sequence for encoding \"%s\": 0x%s",
                                        pg_enc2name_tbl[encoding].name,
-                                       buf)));
+                                       buf),
+                        errhint("This failure can also happen if the byte sequence does not "
+                                        "match the encoding expected by the server, which is controlled "
+                                        "by \"client_encoding\".")));
 }
 
 /*