From a3132359fd633d63014e5a8cc0f5c119d6449f71 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 22 Aug 2006 12:11:28 +0000 Subject: [PATCH] In new "invalid byte sequence" error hint, call it "error", not "failure". --- src/backend/utils/mb/wchar.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/utils/mb/wchar.c b/src/backend/utils/mb/wchar.c index 0a8d70fe8f..b33cbef49f 100644 --- 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.56 2006/08/22 03:30:20 momjian Exp $ + * $PostgreSQL: pgsql/src/backend/utils/mb/wchar.c,v 1.57 2006/08/22 12:11:28 momjian Exp $ * * WIN1250 client encoding updated by Pavel Behal * @@ -1487,7 +1487,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\"."))); } -- 2.40.0