| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER EXTENSION UPGRADE, v3 |
| Date: | 2011-02-10 21:39:41 |
| Message-ID: | A2B7CFC1-5B85-4ACE-A3D5-5F0820952938@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2011-02-10 21:41:47 | Re: ALTER EXTENSION UPGRADE, v3 |
| Previous Message | Tom Lane | 2011-02-10 21:38:15 | Re: ALTER EXTENSION UPGRADE, v3 |