Re: ALTER EXTENSION ... UPGRADE; - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: ALTER EXTENSION ... UPGRADE;
Date
Msg-id m2bp4t2wq3.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: ALTER EXTENSION ... UPGRADE;  (Josh Berkus <josh@agliodbs.com>)
Responses Re: ALTER EXTENSION ... UPGRADE;  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> I think that each contrib needs its own version numbers.  The reason
> being that most minor updates don't touch contrib.

Fair enough. What are the version numbers of each current contribs?

> Also, once extensions and pgxn are operating full swing, I see contrib
> going away anyway ...

No, not all of them. Most of them are in the tree as show cases or for
core developers to easily check they just didn't break an important part
of the system from an external viewpoint, or to give examples on how to
upgrade external extension code between major releases.

The part that will drop in interest is the one where customers are not
trusting the extension mechanism and third-party software enough to
grant them landing into their production environments. Maybe. Given some
years and a good track record.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ALTER EXTENSION ... UPGRADE;
Next
From: Andrew Dunstan
Date:
Subject: Re: ALTER EXTENSION ... UPGRADE;