Re: ALTER EXTENSION UPGRADE, v3

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ALTER EXTENSION UPGRADE, v3
Date: 2011-02-11 20:52:37
Message-ID: m2oc6i47l6.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2011-02-11 20:55:18 Re: ALTER EXTENSION UPGRADE, v3
Previous Message Heikki Linnakangas 2011-02-11 20:50:55 Re: review: FDW API