| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
| Cc: | Joseph Adams <joeyadams3(dot)14159(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |
| Date: | 2010-09-18 02:46:38 |
| Message-ID: | AANLkTinaKZ5HSbctAqzmk8XcKBGztzsieQ-fi4vMVwc8@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 17, 2010 at 10:28 PM, Itagaki Takahiro
<itagaki(dot)takahiro(at)gmail(dot)com> wrote:
> One of my proposal is we don't have to keep the original input text.
> We store JSON data in effective internal formats. If users want to get
> human-readable output, they can use stringify() with indentation option.
There's a trade-off here: this will make some things faster, but other
things slower. Probably some discussion of the pros and cons is in
order.
(Also, it's important not to break EXPLAIN (FORMAT JSON), which thinks
that the internal format of JSON is text.)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Itagaki Takahiro | 2010-09-18 03:12:41 | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |
| Previous Message | Bruce Momjian | 2010-09-18 02:33:55 | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |