Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as
Date
Msg-id 1191921136.4223.618.camel@ebony.site
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as
List pgsql-hackers
On Tue, 2007-10-09 at 10:58 +0200, Magnus Hagander wrote:
> On Tue, Oct 09, 2007 at 08:20:45AM +0100, Simon Riggs wrote:
> > On Mon, 2007-10-08 at 17:38 -0400, Robert Treat wrote:
> > > On Monday 08 October 2007 16:29, Magnus Hagander wrote:
> > > > The whole contrib thing confuses a lot of users. Is it included, or
> > > > isn't it?  IMHO, that distinction need to be clear, and I thought we
> > > > were working (if not actively then at least passively) to "retire"
> > > > contrib, moving things either to core or to pgFoundry. Adding yet
> > > > another important feature that's "just in contrib" is making things
> > > > worse, not better.
> > > > IMHO, of course ;-)
> > > >
> > > 
> > > +1.  I felt the same way about pg_standby, which would have been far more 
> > > accessible for 8.2 users had it lived on pg_foundry. 
> > 
> > I think we should move a version of pg_standby to pg_foundry anyway,
> > specifically to support 8.2 users. 
> 
> Are you saying you want two versions of pg_standby, one in contrbi and one
> on pgfoundry, or are you saying we should take the one in contrib away?

I would prefer that we backported pg_standby into 8.2 contrib, so the
solution is where people need it to be. If not...

--  Simon Riggs 2ndQuadrant  http://www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as
Next
From: Magnus Hagander
Date:
Subject: Re: ECPG regression tests