Re: jsonb, unicode escapes and escaped backslashes

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb, unicode escapes and escaped backslashes
Date: 2015-01-27 19:17:44
Message-ID: 54C7E458.9020700@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 01/27/2015 01:40 PM, Tom Lane wrote:

> In particular, I would like to suggest that the current representation of
> \u0000 is fundamentally broken and that we have to change it, not try to
> band-aid around it. This will mean an on-disk incompatibility for jsonb
> data containing U+0000, but hopefully there is very little of that out
> there yet. If we can get a fix into 9.4.1, I think it's reasonable to
> consider such solutions.
>
>

Hmm, OK. I had thought we'd be ruling that out, but I agree if it's on
the table what I suggested is unnecessary.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-01-27 19:28:27 Re: jsonb, unicode escapes and escaped backslashes
Previous Message Andres Freund 2015-01-27 19:16:43 Re: basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe?