| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-28 03:09:22 |
| Message-ID: | 530FFDE2.6020905@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/27/14, 2:11 PM, Josh Berkus wrote:
> This means that, if we have jsonb as an extension, we'll
> eventually be in the position where the recommended json type with all
> the features is an extension, whereas the legacy json type is in core.
Well that wouldn't be a new situation. Compare geometry types vs
postgis, inet vs ip4(r). It's not bad being an extension. You can
iterate faster and don't have to discuss so much. ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-02-28 03:09:52 | Re: jsonb and nested hstore |
| Previous Message | Peter Eisentraut | 2014-02-28 02:53:58 | Re: pgbench help message fix |