From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu, 17 Dec 2015 21:55:23 +0000 (-0500)
Subject: Fix improper initialization order for readline.
X-Git-Tag: REL9_5_0~44
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5ec0aad018c3f36f9bd3e844f20562fb3c5d4590;p=postgresql

Fix improper initialization order for readline.

Turns out we must set rl_basic_word_break_characters *before* we call
rl_initialize() the first time, because it will quietly copy that value
elsewhere --- but only on the first call.  (Love these undocumented
dependencies.)  I broke this yesterday in commit 2ec477dc8108339d;
like that commit, back-patch to all active branches.  Per report from
Pavel Stehule.
---

diff --git a/src/bin/psql/input.c b/src/bin/psql/input.c
index c0c5524af5..2bc065adcf 100644
--- a/src/bin/psql/input.c
+++ b/src/bin/psql/input.c
@@ -341,8 +341,10 @@ initializeInput(int flags)
 		char		home[MAXPGPATH];
 
 		useReadline = true;
-		rl_initialize();
+
+		/* these two things must be done in this order: */
 		initialize_readline();
+		rl_initialize();
 
 		useHistory = true;
 		using_history();