| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: 9.4 release notes |
| Date: | 2014-05-05 16:06:17 |
| Message-ID: | 20140505160617.GI29541@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 5, 2014 at 11:28:21AM -0400, Andrew Dunstan wrote:
> No, I think you're missing the point of what I'm saying, and I think
> the addition is at best misleading. I would avoid talk of key value
> pairs, anyway, that's not all that's in a json document (it might be
> an array, for example).
>
> How about:
>
> This data type allows for faster access to values in the json document and faster and more useful indexing of json.
OK, I used you wording. You are right I didn't understand it.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2014-05-05 16:10:17 | Re: tab completion for setting search_path |
| Previous Message | Andres Freund | 2014-05-05 15:58:35 | Re: pgsql: Revive line type |