| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Terry Laurenzo <tj(at)laurenzo(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |
| Date: | 2010-11-21 17:40:07 |
| Message-ID: | 75E6BD8C-E861-4AA3-B447-74EFADA756EE@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 20, 2010, at 9:31 PM, Terry Laurenzo wrote:
> Assuming that the JSON datatype (at a minimum) normalizes text for storage, then the text storage option accounts for about the most expensive path but with none of the benefits of an internal binary form (smaller size, ability to cheaply perform non-trivial manipulation within the database server).
>
> Of course, just having a JSON datatype that blindly stores text will beat everything, but I'm getting closer to thinking that the binary option is worth the tradeoff.
>
> Comments?
benchmarks++
Nice to have some data points for this discussion.
Best,
David, still hoping for the JSON data type in 9.1…
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-11-21 18:03:17 | Re: ALTER OBJECT any_name SET SCHEMA name |
| Previous Message | Robert Haas | 2010-11-21 17:31:02 | Re: Improving prep_buildtree used in VPATH builds |