| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Oleg Bartunov <obartunov(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)heroku(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-03-07 17:00:48 |
| Message-ID: | 20140307170048.GA16324@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-03-07 17:30:15 | Re: API change advice: Passing plan invalidation info from the rewriter into the planner? |
| Previous Message | Andrew Dunstan | 2014-03-07 16:57:48 | Re: jsonb and nested hstore |