Re: jsonb and nested hstore

Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Wed, Feb 5, 2014 at 10:22 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> The whole reason we have jsonb is to avoid reparsing where possible

> Sure; but on the server side. The wire format is for handling client
> concerns. For example, the case you're arguing for would be for libpq
> client to extract as jsonb as binary, manipulate it on a binary level,
> then send it back as binary. I find this case to be something of a
> stretch.

I'm with Merlin in thinking that the case for exposing a binary format
to clients is pretty weak, or at least a convincing use-case has not
been shown. Given the concerns upthread about security hazards in the
patch's existing recv code, and the fact that it's already February,
switching to "binary is the same as text" may well be the most prudent
path here.

regards, tom lane