In new "invalid byte sequence" error hint, call it "error", not
authorBruce Momjian <[email protected]>
Tue, 22 Aug 2006 12:11:38 +0000 (12:11 +0000)
committerBruce Momjian <[email protected]>
Tue, 22 Aug 2006 12:11:38 +0000 (12:11 +0000)
"failure".

src/backend/utils/mb/wchar.c

index 6e2056ffe81e2b8d81faa0360ef740c68d968128..78809943b0db0339317f9ee61408756b515976b1 100644 (file)
@@ -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\".")));
 }