Re: jsonb, unicode escapes and escaped backslashes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: jsonb, unicode escapes and escaped backslashes
Date: 2015-01-28 18:30:16
Message-ID: 4579.1422469816@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> Am I missing something or has there been no consideration in this "forbid"
> plan on whether users will be able to retrieve, even if partially
> incorrectly, any jsonb data that has already been stored?

Data that's already been stored would look like the six characters \u0000,
which indeed might have been what it was anyway, since part of the
problem here is that we fail to distinguish "\\u0000" from "\u0000".

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-01-28 18:38:51 Re: Misaligned BufferDescriptors causing major performance problems on AMD
Previous Message Merlin Moncure 2015-01-28 18:26:01 Re: hung backends stuck in spinlock heavy endless loop