From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Guillaume Lelarge <guillaume@lelarge.info>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Cc: Peter Eisentraut <peter_e@gmx.net>
Subject: Re: RFC: Remove contrib entirely
Date: Fri, 29 May 2015 08:01:37 +0200 (CEST)
Message-ID: <alpine.DEB.2.10.1505290750050.24520@sto> (raw)
In-Reply-To: <CAECtzeWrOT7LgNABk9V=CWCATHYQMxLdE9etG3iHGADqa8kOQA@mail.gmail.com>
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: coelho@cri.ensmp.fr, guillaume@lelarge.info, jd@commandprompt.com, sfrost@snowman.net, peter_e@gmx.net
Subject: Re: RFC: Remove contrib entirely
In-Reply-To: <alpine.DEB.2.10.1505290750050.24520@sto>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox