pgsql: Make tab-completion tests more robust. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Make tab-completion tests more robust.
Date
Msg-id E1inp7D-0002lD-B1@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Make tab-completion tests more robust.

Depending on as-yet-incompletely-explained factors, readline/libedit
might choose to emit screen-control escape sequences as part of
repainting the display.  I'd tried to make the test patterns avoid
matching parts of the output that are likely to contain such, but
it seems that there's really no way around matching them explicitly
in some places, unless we want to just give up testing some behaviors
such as display of alternatives.

Per report from Peter Geoghegan.

Discussion: https://postgr.es/m/CAH2-WznPzfWHu8PQwv1Qjpf4wQVPaaWpoO5NunFz9zsYKB4uJA@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/fac1c04feca6d01f2d324088c5899485f55b6217

Modified Files
--------------
src/bin/psql/t/010_tab_completion.pl | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Make better use of ParseState in ProcessUtility
Next
From: Noah Misch
Date:
Subject: pgsql: Skip memcpy(x, x) in qunique().