Don't try to force TERM to a fixed value in tab-completion test.

Right at the moment, this is making things worse not better in the
buildfarm.  I'm not happy with anything about the current state,
but let's at least try to have a green buildfarm report while further
investigation continues.

Discussion: https://postgr.es/m/23181.1578167938@sss.pgh.pa.us

diff --git a/src/bin/psql/t/010_tab_completion.pl b/src/bin/psql/t/010_tab_completion.pl
index 1dc87b504fab7169ed2d35b4df0fa5149a7a8f21..0f1d596b2bff4db1b9001a564dd14999a2a2dd8f 100644 (file)
--- a/src/bin/psql/t/010_tab_completion.pl
+++ b/src/bin/psql/t/010_tab_completion.pl
@@ -41,9 +41,6 @@ $ENV{PSQL_HISTORY} = $historyfile;
 # Debug investigation
 note "TERM is set to '" . ($ENV{TERM} || "<undef>") . "'";
 
-# Ensure that readline/libedit puts out xterm escapes, not something else.
-$ENV{TERM} = 'xterm';
-
 # regexp to match one xterm escape sequence (CSI style only, for now)
 my $escseq = "(\e\\[[0-9;]*[A-Za-z])";