Re: Core Extensions relocation

Поиск
Список
Период
Сортировка
От Josh Berkus
Тема Re: Core Extensions relocation
Дата
Msg-id 4EC1B8A5.7070704@agliodbs.com
обсуждение исходный текст
Ответ на Re: Core Extensions relocation  (Greg Smith <greg@2ndQuadrant.com>)
Ответы Re: Core Extensions relocation
Re: Core Extensions relocation
Re: Core Extensions relocation
Список pgsql-hackers
Greg,

So I'm a bit unclear on why most of the optional data types were
excluded from your list of Core Extensions.  I would regard the
following as stable and of general utility:

btree_gin
btree_gist
citext
dblink
file_fdw
fuzzystrmatch
hstore
intarray
isn
ltree
pgcrypto
pg_trgm
unaccent
uuid-ossp

These should, in my opinion, all be Core Extensions.  I'd go further to
say that if something is materially an extension (as opposed to a tool
or a code example), and we're shipping it with the core distribution, it
either ought to be a core extension, or it should be kicked out to PGXN.

Am I completely misunderstanding what you're trying to accomplish here?

... also, why is there still a "tsearch2" contrib module around at all?

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


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

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: Core Extensions relocation
Следующее
От: Thom Brown
Дата:
Сообщение: Re: Core Extensions relocation