Re: RFC: Remove contrib entirely

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RFC: Remove contrib entirely
Date: 2015-05-29 01:25:22
Message-ID: 5567C002.90203@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 05/28/2015 04:22 PM, Joshua D. Drake wrote:
>
> On 05/28/2015 01:11 PM, Andrew Dunstan wrote:
>
>>
>> This seems to come up regularly. Maybe we should put it in an FAQ
>> somewhere. The barriers to making non-core types into core types are
>> very very high, possibly insurmountable. This is pretty much not an
>> option.
>
> O.k., then either:
>
> * We install it by default and document that it is available (and how
> to enable it)
>
> * Push it out of core and let it be happy wherever Theory wants it to be
>

I'd be ok with installing it by default.

But the case that's a lot harder to require to be always installed is
pgcrypto, as has often been discussed in the past.

In any case, we will always want to have some loadable modules, not
least because it's a part of eating our own dog food.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-05-29 01:31:56 Re: Free indexed_tlist memory explicitly within set_plan_refs()
Previous Message Gavin Flower 2015-05-29 01:22:27 Re: pg_upgrade resets timeline to 1