Remove sometimes inaccurate error hint about source of wrongly encoded data.
authorAndrew Dunstan <andrew@dunslane.net>
Mon, 4 Jan 2010 20:38:31 +0000 (20:38 +0000)
committerAndrew Dunstan <andrew@dunslane.net>
Mon, 4 Jan 2010 20:38:31 +0000 (20:38 +0000)
src/backend/utils/mb/wchar.c

index 9bff635b883b70aae824383f5bc37b5b5cebf92a..e164866a77cb924faac803ed8eecad1563b27892 100644 (file)
@@ -1,7 +1,7 @@
 /*
  * conversion functions between pg_wchar and multibyte streams.
  * Tatsuo Ishii
- * $PostgreSQL: pgsql/src/backend/utils/mb/wchar.c,v 1.73 2009/06/11 14:49:05 momjian Exp $
+ * $PostgreSQL: pgsql/src/backend/utils/mb/wchar.c,v 1.74 2010/01/04 20:38:31 adunstan Exp $
  *
  */
 /* can be used in either frontend or backend */
@@ -1608,10 +1608,7 @@ 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),
-                 errhint("This error can also happen if the byte sequence does not "
-                       "match the encoding expected by the server, which is controlled "
-                                 "by \"client_encoding\".")));
+                                       buf)));
 }
 
 /*