Testing Extension Upgrade Paths

Поиск
Список
Период
Сортировка
От Jeremy Finzel
Тема Testing Extension Upgrade Paths
Дата
Msg-id CAMa1XUi849bYaXCPbAUTHJ-ued8NK_Yihu_JwvdJWJEb73v3Xw@mail.gmail.com
обсуждение исходный текст
Ответы Re: Testing Extension Upgrade Paths  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
Hello - 

I understand how to setup a regression suite for a postgres extension, but what I'm not clear on from the docs is if there is a pattern that exists for testing not only the latest version of an extension, but also an upgraded previous version.

For example, I am developing version 1.1, and the test suite runs fine for 1.1.

But I want to install the extension at 1.0, do a few things, then upgrade to 1.1 and run N tests over again from this path.

I have in mind something like an environment variable or something where you could run the suite twice with the variation being a direct install at the highest version, or an upgrade from a previous version.  Please excuse my ignorance!

Is there any straightforward way to do this that doesn't involve manually copying tests?

Thank you!
Jeremy

P.S. is this the right list for extension dev questions ???

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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Mention ordered datums in PartitionBoundInfoData comment
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] parallel.c oblivion of worker-startup failures