Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as
| От | Robert Treat |
|---|---|
| Тема | Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as |
| Дата | |
| Msg-id | 200710101141.58041.xzilla@users.sourceforge.net обсуждение исходный текст |
| Ответ на | Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as (Andrew Dunstan <andrew@dunslane.net>) |
| Ответы |
Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as
|
| Список | pgsql-hackers |
On Wednesday 10 October 2007 10:57, Andrew Dunstan wrote:
> Robert Treat wrote:
> > On Wednesday 10 October 2007 02:09, Simon Riggs wrote:
> >> On Wed, 2007-10-10 at 01:14 -0300, Euler Taveira de Oliveira wrote:
> >>> Simon Riggs wrote:
> >>>> I would prefer that we backported pg_standby into 8.2 contrib, so the
> >>>> solution is where people need it to be. If not...
> >>>
> >>> Don't know about the policy to put things in already-released-version
> >>> but if it's not the case, we could at least put the code somewhere in
> >>> the ftp.postgresql.org. IMHO pgfoundry project will confuse people.
> >>
> >> Both: ftp and pgfoundry.
> >
> > Putting it on pgfoundry would automatically put it in the ftp tree
> > (ftp://ftp.postgresql.org/pub/projects/pgFoundry). If it was to go on
> > pgfoundry (which I'd recommend) I'd suggest removing it from 8.3 contrib
> > before we release (cause having it in both places is really going to
> > cause confusion)
>
> One of pgfoundry's explicit purposes is for backports of features.
I can't think of any contrib modules we've added that also required backwards
comptible modules to be released on foundry at the same time. ISTM that such
a requirement would be an argument that such a thing doesn't belong in
contrib at all.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
В списке pgsql-hackers по дате отправления: