Re: ALTER EXTENSION ... UPGRADE;

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Cc: "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER EXTENSION ... UPGRADE;
Date: 2010-12-13 15:18:51
Message-ID: AANLkTimB_szzzXTOKqZcAb+uTEbXLyBgtcqr5q+521S7@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 13, 2010 at 9:55 AM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)fr> wrote:

>> Again, I'ld love for the "version" to support some sort of prefix or
>> wildcard matching, so I could do:
>>     upgrade-1.* =  $EXT-upgrade-1.sql
>>     upgrade-2.* =  $EXT-upgrade-2.sql
>
> Problem is: what to do if a single upgrade matches more than one line?
> The only safe answer is to error out and refuse to upgrade but that
> ain't nice to the user. How much is that a problem here?

To get a wildcard match (or a prefix match) for version upgrades, I'ld
be willing to have that error if I give a bad set of version matches.
If only have those 2 lines to manage, it's a lot more likely I won't
mess them up than if I have to manage 30 almost identical lines and
not miss/duplicate a version.

;-)

--
Aidan Van Dyk                                             Create like a god,
aidan(at)highrise(dot)ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-12-13 15:33:27 Re: hstores in pl/python
Previous Message Tom Lane 2010-12-13 15:14:29 Re: GiST insert algorithm rewrite