Re: jsonb and nested hstore
| От | Hannu Krosing |
|---|---|
| Тема | Re: jsonb and nested hstore |
| Дата | |
| Msg-id | 52F89EDB.8080405@krosing.net обсуждение исходный текст |
| Ответ на | Re: jsonb and nested hstore (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: jsonb and nested hstore
|
| Список | pgsql-hackers |
On 02/05/2014 06:48 PM, Tom Lane wrote: > Andrew Dunstan <andrew@dunslane.net> writes: >> On 02/05/2014 11:40 AM, Tom Lane wrote: >>> switching to "binary is the same as text" may well be the most prudent >>> path here. >> If we do that we're going to have to live with that forever, aren't we? > Yeah, but the other side of that coin is that we'll have to live forever > with whatever binary format we pick, too. If it turns out to be badly > designed, that could be much worse than eating some parsing costs during > dump/restore. The fastest and lowest parsing cost format for "JSON" is tnetstrings http://tnetstrings.org/ why not use it as the binary wire format ? It would be as binary as it gets and still be generally parse-able by lots of different platforms, at leas by all of these we care about. Cheers Hannu
В списке pgsql-hackers по дате отправления: