Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
Дата
Msg-id YoHhWD5vQzb2mmiF@paquier.xyz
обсуждение исходный текст
Ответ на Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set  (Noah Misch <noah@leadboat.com>)
Ответы Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set  (Noah Misch <noah@leadboat.com>)
Список pgsql-hackers
On Sat, May 14, 2022 at 01:27:28AM -0700, Noah Misch wrote:
> Here, I requested the rationale for the differences you had just described.
> You made a choice to stop testing one list of database names and start testing
> a different list of database names.  Why?

Because the shape of the new names does not change the test coverage
("regression" prefix or the addition of the double quotes with
backslashes for all the database names), while keeping the code a bit
simpler.  If you think that the older names are more adapted, I have
no objections to use them, FWIW, which is something like the patch
attached would achieve.

This uses the same convention as vcregress.pl before 322becb, but not
the one of test.sh where "regression" was appended to the database
names.
--
Michael

Вложения

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: list of TransactionIds
Следующее
От: Dilip Kumar
Дата:
Сообщение: Re: Make relfile tombstone files conditional on WAL level