postgres.git / summary / log / commit / refs

commit    9025af3ed039dd3bb9286b5af2fbdb29b9eb204e
Author:   Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date:     Sat Apr 08 10:32:38 2017 +0000

    Fix the new SASLprep tests to work with non-UTF-8 locales.
    
    Fix by forcing database encoding to UTF-8, regardless of the current
    locale.
    
    Pointed out by Tom Lane.
    
    Discussion: https://www.postgresql.org/message-id/8934.1491614631@sss.pgh.pa.us


 src/test/authentication/t/002_saslprep.pl | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/src/test/authentication/t/002_saslprep.pl b/src/test/authentication/t/002_saslprep.pl
index 0c18528e7af..7e373ed7bf4 100644
--- a/src/test/authentication/t/002_saslprep.pl
+++ b/src/test/authentication/t/002_saslprep.pl
@@ -42,9 +42,10 @@ SKIP:
 {
 	skip "authentication tests cannot run on Windows", 12 if ($windows_os);
 
-	# Initialize master node
+	# Initialize master node. Force UTF-8 encoding, so that we can use non-ASCII
+	# characters in the passwords below.
 	my $node = get_new_node('master');
-	$node->init;
+	$node->init(extra => ['--locale=C', '--encoding=UTF8']);
 	$node->start;
 
 	# These tests are based on the example strings from RFC4013.txt,


[parent: f0e44021dfbd]