From 4b98b613f6980d4d14dada062b47322132107144 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Tue, 18 Aug 2009 16:00:50 +0000 Subject: [PATCH] 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. --- contrib/unaccent/expected/unaccent.out | 7 +++++++ contrib/unaccent/sql/unaccent.sql | 3 +++ 2 files changed, 10 insertions(+) diff --git a/contrib/unaccent/expected/unaccent.out b/contrib/unaccent/expected/unaccent.out index 8d197c50be..a09e00fe5b 100644 --- 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 71ab5bb435..ede938d479 100644 --- 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'); -- 2.11.0