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

From Bruce Momjian
Subject Re: jsonb and nested hstore
Date
Msg-id 20140307170048.GA16324@momjian.us
Whole thread Raw
In response to Re: jsonb and nested hstore  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: jsonb and nested hstore  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Fri, Mar  7, 2014 at 11:57:48AM -0500, Andrew Dunstan wrote:
> >If they can be done for 9.4, great, if not, we have to decide if these
> >suboptimal cases are enough for us to delay the data type until 9.5.  I
> >don't know the answer, but I have to ask the question.
> >
> 
> AFAIK, there is no sacrifice of optimality. hstore2 and jsonb were
> essentially two ways of spelling the same data, the domains were
> virtually identical (hstore might have been a bit more liberal about
> numeric input).

OK, it sounds like the adjustments are minimal, like not using the
high-order bit.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: jsonb and nested hstore
Next
From: Tom Lane
Date:
Subject: Re: API change advice: Passing plan invalidation info from the rewriter into the planner?