Re: [PATCH] Support % wildcard in extension upgrade filenames
В списке pgsql-hackers по дате отправления:
| От | 'Sandro Santilli' |
|---|---|
| Тема | Re: [PATCH] Support % wildcard in extension upgrade filenames |
| Дата | |
| Msg-id | 20221116230933.6ynksku66i436ozm@c19 обсуждение исходный текст |
| Ответ на | RE: [PATCH] Support % wildcard in extension upgrade filenames ("Regina Obe" <lr@pcorp.us>) |
| Ответы |
RE: [PATCH] Support % wildcard in extension upgrade filenames
Re: [PATCH] Support % wildcard in extension upgrade filenames |
| Список | pgsql-hackers |
On Sun, Nov 13, 2022 at 11:46:50PM -0500, Regina Obe wrote: > > Re: Sandro Santilli > > > I'm attaching an updated version of the patch. This time the patch is > > > tested. Nothing changes unless the .control file for the subject > > > extension doesn't have a "wildcard_upgrades = true" statement. > > > > > > When wildcard upgrades are enabled, a file with a "%" symbol as the > > > "source" part of the upgrade path will match any version and > > > > Fwiw I believe wildcard_upgrades isn't necessary in the .control file. > > If there are no % files, none would be used anyway, and if there are, it's > clear > > it's meant as wildcard since % won't appear in any remotely sane version > > number. > > I also like the idea of skipping the wildcard_upgrades syntax. > Then there is no need to have a conditional control file for PG 16 vs. older > versions. Here we go. Attached a version of the patch with no "wildcard_upgrades" controlling it. --strk;
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера