Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
От | Tom Lane |
---|---|
Тема | Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set |
Дата | |
Msg-id | 502623.1648702814@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set |
Список | pgsql-hackers |
Michael Paquier <michael@paquier.xyz> writes: > So, any particular feelings about this patch? This has been around > for a couple of months/years now, so it could be a good time to do the > switch now rather than wait an extra year, or even the beginning of > the next release cycle. And the buildfarm is already able to handle > that in its code based on the last release, by skipping the upgrade > check if it finds a pg_upgrade/t/ subdirectory. There's still about a third of the buildfarm running older client releases --- I count 2 REL_8 2 REL_10 13 REL_11 6 REL_12 16 REL_13.1 89 REL_14 How well does this patch work with pre-14 buildfarm clients? regards, tom lane
В списке pgsql-hackers по дате отправления: