Re: jsonb and nested hstore - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: jsonb and nested hstore
Date
Msg-id CAHyXU0yGcOmKe2rsAyRTC=FPsY6D8X-w9m0TC0ZZ7BEeHbwLtA@mail.gmail.com
Whole thread Raw
In response to Re: jsonb and nested hstore  (Bruce Momjian <bruce@momjian.us>)
Responses Re: jsonb and nested hstore  (Bruce Momjian <bruce@momjian.us>)
Re: jsonb and nested hstore  (Robert Haas <robertmhaas@gmail.com>)
Re: jsonb and nested hstore  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Wed, Mar 5, 2014 at 8:39 AM, Bruce Momjian <bruce@momjian.us> wrote:
> So, I am going to ask a back-track question and ask why we can't move
> hstore into core.

This is exactly the opposite of what should be happening.  Now, jsonb
might make it into core because of the json precedent but the entire
purpose of the extension system is stop dumping everything in the
public namespace.   Stuff 'in core' becomes locked in stone, forever,
because of backwards compatibility concerns, which are IMNSHO, a
bigger set of issues than even pg_upgrade related issues.  Have we
gone through all the new hstore functions and made sure they don't
break existing applications?  Putting things in core welds your only
escape hatch shut.

*All* non-sql standard types ought to be in extensions in an ideal world.

merlin



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Review: Patch FORCE_NULL option for copy COPY in CSV mode
Next
From: Alvaro Herrera
Date:
Subject: Re: Fwd: patch: make_timestamp function