pgsql: Ignore more environment variables in TAP tests

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема pgsql: Ignore more environment variables in TAP tests
Дата
Msg-id E1lodTP-0003tD-Ts@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Ignore more environment variables in TAP tests

Various environment variables were not getting reset in the TAP tests,
which would cause failures depending on the tests or the environment
variables involved.  For example, PGSSL{MAX,MIN}PROTOCOLVERSION could
cause failures in the SSL tests.  Even worse, a junk value of
PGCLIENTENCODING makes a server startup fail.  The list of variables
reset is adjusted in each stable branch depending on what is supported.

While on it, simplify a bit the code per a suggestion from Andrew
Dunstan, using a list of variables instead of doing single deletions.

Reviewed-by: Andrew Dunstan, Daniel Gustafsson
Discussion: https://postgr.es/m/YLbjjRpucIeZ78VQ@paquier.xyz
Backpatch-through: 9.6

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/8279f68a1b13d58a0c9869a60081009d8995e4df

Modified Files
--------------
src/test/perl/TestLib.pm | 43 ++++++++++++++++++++++++++++++++-----------
1 file changed, 32 insertions(+), 11 deletions(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Re-allow custom GUC names that have more than two components.
Следующее
От: David Rowley
Дата:
Сообщение: pgsql: Standardize usages of appendStringInfo and appendPQExpBuffer