Re: ALTER EXTENSION UPGRADE, v3 - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: ALTER EXTENSION UPGRADE, v3
Date
Msg-id A2B7CFC1-5B85-4ACE-A3D5-5F0820952938@kineticode.com
Whole thread Raw
In response to Re: ALTER EXTENSION UPGRADE, v3  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Feb 10, 2011, at 1:38 PM, Tom Lane wrote:

> I don't deny that there are risks here.  But I think the value of being
> able to move an extension when it is safe outweighs the difficulty that
> sometimes it isn't safe.  I think we can leave making it safer as a
> topic for future investigation.
> 
> Dimitri did suggest treating an extension as nonrelocatable if there is
> any other extension installed that depends on it.  But that seems like
> more of a kluge than a nice solution, primarily because it does nothing
> for the loose-object risks.  I'd rather just document that moving an
> extension post-installation might break things, and leave it at that for
> now.

+1

David



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ALTER EXTENSION UPGRADE, v3
Next
From: Aidan Van Dyk
Date:
Subject: Re: ALTER EXTENSION UPGRADE, v3