| 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:24:13 |
| Message-ID: | 5235F2D1-890F-4D05-9C29-C14E2564A132@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 10, 2011, at 1:22 PM, Tom Lane wrote:
> Well, okay, let's go with that plan then. If we don't need to assume
> anything more than equality of version names being meaningful, I think
> chaining update scripts automatically should solve most of the
> complaints here. People who really want to maintain shortcut scripts
> still could, but I think it'd be an unusual case.
Yes, I think that this is a great solution. I only have to create on upgrade script for each release, and I don't have to worry about concatenating anything or be required to change my versioning algorithm.
+1
Finally, a solution!
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Singer | 2011-02-10 21:26:13 | Re: pl/python custom exceptions for SPI |
| Previous Message | Andrew Dunstan | 2011-02-10 21:23:17 | Re: Revised patches to add table function support to PL/Tcl (TODO item) |