Re: RFC: Remove contrib entirely

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RFC: Remove contrib entirely
Date: 2015-06-05 13:42:45
Message-ID: CANP8+jKWcZEv75BPO4dxsDNa+yMGriZ3Zr8MJosnJ33hPGHxcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 29 May 2015 at 02:50, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:

> On 5/28/15 3:35 PM, Stephen Frost wrote:
> > What we would need for this is an 'extensions' directory, or similar,
> > and a clear definition of what the requirements are around getting into
> > it are. With that, we could decide for each module currently in contrib
> > if it should go into the 'extensions' directory. I'm not sure that we
> > would necessairly have to remove the contrib module or any modules which
> > are deemed to not be appropriate for the 'extensions' directory.
>
> This seems reasonable to me. It's in line with the recent move from
> contrib to bin. It'll just be quite a bit bigger of an undertaking.
> (50 threads to discuss the merits of each module separately?) Maybe
> start by picking the top 5 and sort those out.

+1 for Extensions directory for 9.6

This doesn't seem worth delaying the release for.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2015-06-05 13:45:25 Re: Memory leak with XLogFileCopy since de768844 (WAL file with .partial)
Previous Message Robert Haas 2015-06-05 13:39:20 Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1