Re: ALTER EXTENSION ... UPGRADE;

Поиск
Список
Период
Сортировка
От Dimitri Fontaine
Тема Re: ALTER EXTENSION ... UPGRADE;
Дата
Msg-id m262v1z18w.fsf@2ndQuadrant.fr
обсуждение исходный текст
Ответ на Re: ALTER EXTENSION ... UPGRADE;  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: ALTER EXTENSION ... UPGRADE;  ("David E. Wheeler" <david@kineticode.com>)
Список pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:
> If we assume the target is the current version, then we only need the
> old-version number in the file name, so it doesn't matter how many
> parts it has.

IIUC, that puts even more work on the shoulders of the extension
authors, because the file named foo-1.12.sql is the one used to upgrade
from 1.12. That means that at each release, it's a different file
content, it's there to upgrade to a newer release.

Well it works too, of course, and we don't care how many dashes we find
in the filename, it's extension-version.sql. I'd be ok with that too.


So, we have a sound proposal for the ALTER EXTENSION UPGRADE command,
which comes later. So we keep version numbers in the CREATE EXTENSION
patch and the control files, and remove the facility to get this number
from the Makefile. Is that right?

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: create tablespace fails silently, or succeeds improperly
Следующее
От: Tom Lane
Дата:
Сообщение: Re: ALTER EXTENSION ... UPGRADE;