Print the actual DB encoding in the unaccent regression test.

This is to help make it more obvious what the problem is, if the
encoding isn't what the test expects.

diff --git a/contrib/unaccent/expected/unaccent.out b/contrib/unaccent/expected/unaccent.out
index 8d197c50be73cb28bad9ae769a0e35b2edbb00ad..a09e00fe5b1394eeea1ea5a875968b86aabaee8b 100644 (file)
--- a/contrib/unaccent/expected/unaccent.out
+++ b/contrib/unaccent/expected/unaccent.out
@@ -1,6 +1,13 @@
 SET client_min_messages = warning;
 \set ECHO none
 RESET client_min_messages;
+-- must have a UTF8 database
+SELECT getdatabaseencoding();
+ getdatabaseencoding 
+---------------------
+ UTF8
+(1 row)
+
 SET client_encoding TO 'KOI8';
 SELECT unaccent('foobar');
  unaccent 

diff --git a/contrib/unaccent/sql/unaccent.sql b/contrib/unaccent/sql/unaccent.sql
index 71ab5bb43583f89c6625adfbed802b9af09ac6fa..ede938d4795bddec457b21c56c105748ba766adf 100644 (file)
--- a/contrib/unaccent/sql/unaccent.sql
+++ b/contrib/unaccent/sql/unaccent.sql
@@ -4,6 +4,9 @@ SET client_min_messages = warning;
 \set ECHO all
 RESET client_min_messages;
 
+-- must have a UTF8 database
+SELECT getdatabaseencoding();
+
 SET client_encoding TO 'KOI8';
 
 SELECT unaccent('foobar');