Re: Change of extension name to new name
От | Tom Lane |
---|---|
Тема | Re: Change of extension name to new name |
Дата | |
Msg-id | 1776.1476333473@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Change of extension name to new name (Haribabu Kommi <kommi.haribabu@gmail.com>) |
Ответы |
Re: Change of extension name to new name
|
Список | pgsql-hackers |
Haribabu Kommi <kommi.haribabu@gmail.com> writes: > As we are planning to change an extension name from one name to another > name because of additional features that are added into this extension, The usual approach to that is just to increase the version number. Why is it necessary to change the name? > I just thought of adding the support of (ALTER EXTENSION name RENAME To > newname), this can be executed before executing the pg_upgrade to the new > extension name that is available in the > newer version. And if the user forgets to do that before upgrading? Not to mention that the extension is mostly broken the moment its SQL name no longer corresponds to the on-disk control file name. This seems like a non-solution. In general, once you've shipped something, changing its name is a huge pain both for you and your users. Just say no. regards, tom lane
В списке pgsql-hackers по дате отправления: