| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Christophe Pettus <xof(at)thebuild(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-03-05 18:05:37 |
| Message-ID: | 53176771.1040508@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/05/2014 09:26 AM, Robert Haas wrote:
>> > What _would_ be interesting is to move all the hstore code into core,
>> > and have hstore contrib just call the hstore core parts. That way, you
>> > have one copy of the code, it is shared with JSONB, but hstore remains
>> > as an extension that you can change or remove later.
> That seems like an approach possibly worth investigating. It's not
> too different from what we did when we moved text search into core.
> The basic idea seems to be that we want jsonb in core, and we expect
> it to replace hstore, but we can't get just get rid of hstore because
> it has too many users
Yes, please! This was the original approach that we talked about and
everyone agreed to, and what Andrew has been trying to implement.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2014-03-05 18:40:59 | Re: [PATCH] Negative Transition Aggregate Functions (WIP) |
| Previous Message | Robert Haas | 2014-03-05 18:00:58 | Re: decoding typos... |