Date: Fri, 29 May 2015 08:01:37 +0200 (CEST)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Guillaume Lelarge <guillaume@lelarge.info>
cc: "Joshua D. Drake" <jd@commandprompt.com>,
 Stephen Frost <sfrost@snowman.net>,
 PostgreSQL Developers <pgsql-hackers@postgresql.org>,
 Peter Eisentraut <peter_e@gmx.net>
Subject: Re: RFC: Remove contrib entirely
In-Reply-To: 
 <CAECtzeWrOT7LgNABk9V=CWCATHYQMxLdE9etG3iHGADqa8kOQA@mail.gmail.com>
Message-ID: <alpine.DEB.2.10.1505290750050.24520@sto>
References: <55674016.80005@commandprompt.com>
 <20150528193556.GH26667@tamriel.snowman.net> <5567C5EB.3070703@gmx.net>
 <5567CB9E.1030502@commandprompt.com>
 <20150529031004.GU26667@tamriel.snowman.net>
 <5567DDBA.8020403@commandprompt.com>
 <CAECtzeWrOT7LgNABk9V=CWCATHYQMxLdE9etG3iHGADqa8kOQA@mail.gmail.com>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


> FWIW, I don't mind which one we put in core and which one we put out of
> core. But I like Joshua's idea of getting rid of contribs and pushing them
> out as any other extensions.

Hmmm.

I like the contrib directory as a living example of "how to do an 
extension" directly available in the source tree. It also allows to test 
in-tree that the extension mechanism works. So I think it should be kept 
at least with a minimum set of dummy examples for this purpose, even if 
all current extensions are moved out.

Also, removing a feature is a regression, and someone is always bound to 
complain... What is the real benefit? ISTM that it is a solution that 
fixes no important problem. Reaching a consensus about what to move here 
or there will consume valuable time that could be spent on more important 
tasks... Is it worth it?

Also moving things into postgresql main sources makes pg heavier for all 
and benefits only to some, so I think that some careful filtering must be 
done bevore moving large contribs there. I guess this is part of the 
argumentation.

-- 
Fabien.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers