Re: ALTER EXTENSION UPGRADE patch v1 - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: ALTER EXTENSION UPGRADE patch v1
Date
Msg-id m2d3obkvq4.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: ALTER EXTENSION UPGRADE patch v1  (David Fetter <david@fetter.org>)
List pgsql-hackers
David Fetter <david@fetter.org> writes:
> The syntax by itself does nothing, but the underlying capability gives
> users:

Ok, now I understand that the syntax you proposed was a shortcut for an
I-want-it-all request :)

> - The ability to have versions of software on different databases on
>   the same system.
>
> - The ability to do deterministic upgrades, rather than just, "upgrade
>   me to the latest, which may be buggy and/or slow things down to
>   avoid a problem I know I don't have."

Both depends on a filesystem organization rework.

> I am not saying that this is a show-stopper.  I *am* saying that
> multiple concurrent versions and deterministic upgrades are common
> enough requests that you shouldn't do things that would prevent those
> in the future.

Would it be useful to have the syntax support in 9.1 already, but which
would only check that the asked-of new version (and current version) are
the one currently available (and installed), and ERROR out otherwise?

I think that syntax-and-check is still doable for 9.1, if there's a will
to get there.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: making an unlogged table logged
Next
From: Josh Berkus
Date:
Subject: Re: We need to log aborted autovacuums