Re: ALTER EXTENSION ... UPGRADE;

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Aidan Van Dyk <aidan(at)highrise(dot)ca>
Cc: "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, 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 14:55:04
Message-ID: 87bp4p90zb.fsf@hi-media-techno.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Aidan Van Dyk <aidan(at)highrise(dot)ca> writes:
> Mainly, because of the situation where I have may versions that can
> all be upgraded from the same script. I'ld much rather distribution
> just 3 scripts (install + 2 upgrades), and a control file with
> something like this (pretend I'm on version 2.6)
> upgragde-1.0 = $EXT-upgrade-1.sql
[...]
> upgrade-2.5 = $EXT-upgrade-2.sql

Thanks for the example.

> 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?

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2010-12-13 14:55:42 Re: Optimize PL/Perl function argument passing [PATCH]
Previous Message Andres Freund 2010-12-13 14:51:14 Re: hstores in pl/python