Re: Core Extensions relocation

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Dimitri Fontaine <dimitri@2ndquadrant.fr>

Cc: Thom Brown <thom@linux.com>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org

Date: 2011-11-16T13:00:47Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Updates to contrib/isn ISBN tables.
- 6d1af7b21807 9.1.0 cited
Add a "LIKE = typename" clause to CREATE TYPE for base types. This allows
- 3f936aacc057 8.4.0 cited

On Tue, Nov 15, 2011 at 5:50 AM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> Thom Brown <thom@linux.com> writes:
>> None of those others perform such a role.  Instead they add additional
>> functionality intended to be utilised as part of general data usage,
>> adding new types, operators, query functions etc.  Maybe the term
>> "core" is inappropriate.  Instead we might wish to refer to them as
>> "utility extensions" or something like that, although that may be just
>> as vague.
>
> The term “core” here intends to show off that those extensions are
> maintained by the core PostgreSQL developer team. If needs be, those
> extensions will get updated in minor releases (crash, bugs, security,
> etc).

Everything in contrib meets that definition, more or less.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company