| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-27 02:43:45 |
| Message-ID: | CAM3SWZQSkirorRpxOkRag_W4O4bXBaxE5Xdm4OJe3qaoj7j-TA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 26, 2014 at 6:29 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Why can't this whole thing be shipped as an extension? It might well
> be more convenient to have the whole thing packaged as an extension
> than to have parts of it in core and parts of it not in core.
That's a good question. I think having everything in contrib would
make it easier to resolve the disconnect between jsonb and hstore. As
things stand, there is a parallel set of functions and operators for
hstore and jsonb, with the former set much larger than the latter. I'm
not terribly happy with that.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-27 03:21:03 | Re: Avoiding deeply nested AND/OR trees in the parser |
| Previous Message | Robert Haas | 2014-02-27 02:33:13 | Re: Changeset Extraction v7.7 |