pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Peter Geoghegan <pg@heroku.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: RFC: Remove contrib entirely
Date: Fri, 29 May 2015 14:09:56 -0700
Message-ID: <5568D5A4.3020002@agliodbs.com> (raw)
In-Reply-To: <WM!55dc4215d3d71da9dd4a8bb3007479f41afcd00bae64bf4ffb96f86b4a135d0f1609c2953c807533ab1bef7ce257301b!@asav-2.01.com>
References: <55674016.80005@commandprompt.com>
	<CAFj8pRC=sccsmdTTVT0XW316-HACK0Fkh8PYAOwVaGSANV80AA@mail.gmail.com>
	<CAECtzeUk_e=uCrwJSz-Z5MbiaqwuFf2gCs9iVkV8LTMesXAZ7Q@mail.gmail.com>
	<CAB7nPqREqu33nQZOnqP-U4F_b643vNZLa24YQ7G8DtEiJ=6U_g@mail.gmail.com>
	<CAFj8pRCAZDQs_ObBb46yfxS-t4rmnC-ujYD2nTCx7jRb2GENGA@mail.gmail.com>
	<WM!cba09fcb04a200dca6aa50578870e5360aceff298c70e35b89e1c83bb825513e3e16610e8589312b97b9deb3c9c52b72!@asav-1.01.com>
	<5568B43E.5030003@agliodbs.com>
	<CAM3SWZR_5+BZ0bfYas0aFqzKtMOzwgeVxLFcoADdzVHk8C_YgA@mail.gmail.com>
	<WM!55dc4215d3d71da9dd4a8bb3007479f41afcd00bae64bf4ffb96f86b4a135d0f1609c2953c807533ab1bef7ce257301b!@asav-2.01.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 05/29/2015 02:08 PM, Peter Geoghegan wrote:
> On Fri, May 29, 2015 at 11:47 AM, Josh Berkus <josh@agliodbs.com> wrote:
>> A. Extra commands and tools which aren't considered general enough, or
>> reliable enough, to be included by default, e.g. pg_standby, pgbench and
>> vacuumlo.
>>
>> B. Developer tools, like spi, start-scripts, and oid2name.
>>
>> C. "Core Extensions", which fall into three further groups:
>>         C1: encryption extensions we can't include in core
>>             for legal reasons (pg_crypto)
>>         C2: example extensions which show useful things about
>>             how to build an extension
>>         C3: Admin extensions which are not core because they carry
>>             risks (e.g. pgstattuple, auto_explain)
>>         C4: Extensions which are generally useful, used, and
>>             maintained with Postgres (e.g. hstore, citext)
> 
> I always liked the idea of organizing contrib along these lines.
> 
> I know that I will never be successful in convincing people to remove,
> say, contrib/isn, which is total garbage, but the next best thing is
> to categorize it in a way that sets expectations very low.

Well, contrib/isn is still useful (I use it).  But there's no good
reason it couldn't be on pgxn.


-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


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



view thread (84+ messages)  latest in thread

Message-ID: <5568D5A4.3020002@agliodbs.com>
Permalink:  ../5568D5A4.3020002@agliodbs.com/
Also on:    postgresql.org/message-id/5568D5A4.3020002@agliodbs.com

 · 

reply
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: josh@agliodbs.com, pg@heroku.com
  Subject: Re: RFC: Remove contrib entirely
  In-Reply-To: <5568D5A4.3020002@agliodbs.com>

* 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