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.
