| From: | David Johnston <polobo(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-19 18:59:27 |
| Message-ID: | 1384887567821-5779227.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gavin Flower-2 wrote
> More seriously, there are obviously variants in what people consider
> useful human readable form of JSON output, but it is probably
> inefficient to store white space.
Enough to matter? Maybe the extra whitespace causes a marginal value to be
toasted but, IIUC, for a value that is going to be toasted anyway the
compression factors for both speed and space is going to make whitespace
considerations insignificant.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/additional-json-functionality-tp5777975p5779227.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-11-19 19:02:28 | Re: additional json functionality |
| Previous Message | Andrew Dunstan | 2013-11-19 18:58:46 | Re: additional json functionality |