Re: RFC: Remove contrib entirely

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: RFC: Remove contrib entirely
Дата
Msg-id CAM3SWZR_5+BZ0bfYas0aFqzKtMOzwgeVxLFcoADdzVHk8C_YgA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: RFC: Remove contrib entirely  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-hackers
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.


-- 
Peter Geoghegan



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [CORE] postpone next week's release
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1