Re: Extensions versus pg_upgrade
| От | Tom Lane |
|---|---|
| Тема | Re: Extensions versus pg_upgrade |
| Дата | |
| Msg-id | 8787.1297355611@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Extensions versus pg_upgrade (Dimitri Fontaine <dimitri@2ndQuadrant.fr>) |
| Ответы |
Re: Extensions versus pg_upgrade
|
| Список | pgsql-hackers |
Dimitri Fontaine <dimitri@2ndQuadrant.fr> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> Actually, it occurs to me that the need for ALTER EXTENSION DROP could
>> be upon us sooner than we think. The cases where an extension upgrade
>> script would need that are
>> (1) you want to remove some deprecated piece of the extension's API;
>> (2) you want to remove some no-longer-needed internal function.
>> Without ALTER EXTENSION DROP it's flat out impossible to do either.
> What if you just DROP FUNCTION in the upgrade script?
That would be rejected because you're not allowed to drop an individual
member object of an extension. (And no, I don't want to have a kluge in
dependency.c that makes that test work differently when
creating_extension.)
regards, tom lane
В списке pgsql-hackers по дате отправления: