In new "invalid byte sequence" error hint, call it "error", not

"failure".

diff --git a/src/backend/utils/mb/wchar.c b/src/backend/utils/mb/wchar.c
index 5635b7320d6949fc2eeb1b24424e29c9695286ee..dcee2b519d51139fdf1b79bcef9b9dac2c1f4031 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.3 2006/08/22 03:38:13 momjian Exp $
+ * $PostgreSQL: pgsql/src/backend/utils/mb/wchar.c,v 1.47.2.4 2006/08/22 12:11:38 momjian Exp $
  *
  * WIN1250 client encoding updated by Pavel Behal
  *
@@ -1326,7 +1326,7 @@ report_invalid_encoding(int encoding, const char *mbstr, int len)
                         errmsg("invalid byte sequence for encoding \"%s\": 0x%s",
                                        pg_enc2name_tbl[encoding].name,
                                        buf),
-                        errhint("This failure can also happen if the byte sequence does not "
+                        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\".")));
 }