Horton

Re: ALTER EXTENSION UPGRADE, v3

Dimitri Fontaine <dimitri@2ndquadrant.fr>

View thread
From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Dimitri Fontaine <dimitri@2ndQuadrant.fr>, Robert Haas <robertmhaas@gmail.com>, "David E. Wheeler" <david@kineticode.com>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2011-02-11T20:52:37Z
Lists: pgsql-hackers 
Tom Lane <tgl@sss.pgh.pa.us> writes:
> Anything that got kicked out to pgfoundry would presumably start acting
> that way.  Anything that's part of core git is going to stay on the same
> release cycle as the core, thank you very much.  Release engineering is
> a big enough headache around here already.

Yeah, I should have inquired before to propose.  I see two solutions
here, one is to just do as you say, the other one would be to have a
separate git repository for extensions.  You can ignore this if only the
default option (your proposal) is sensible…

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