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

From David E. Wheeler
Subject Re: ALTER EXTENSION UPGRADE, v3
Date
Msg-id 5235F2D1-890F-4D05-9C29-C14E2564A132@kineticode.com
Whole thread Raw
In response to Re: ALTER EXTENSION UPGRADE, v3  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ALTER EXTENSION UPGRADE, v3  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List 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
toworry about concatenating anything or be required to change my versioning algorithm. 

+1

Finally, a solution!

Best,

David



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Revised patches to add table function support to PL/Tcl (TODO item)
Next
From: Steve Singer
Date:
Subject: Re: pl/python custom exceptions for SPI