Re: jsonb, unicode escapes and escaped backslashes

On Wed, Jan 28, 2015 at 12:48 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The cause of this bug is commit 0ad1a816320a2b539a51628e2a0b1e83ff096b1d,
> which I'm inclined to think we need to simply revert, not render even
> more squirrely.

Yes, that commit looks broken.  If you convert from text to JSON you
should get a JSON string equivalent to the text you started out with.
That commit departs from that in favor of allowing \uXXXX sequences in
the text being converted to turn into a single character (or perhaps
an encoding error) after a text->json->text roundtrip.  Maybe I
haven't had enough caffeine today, but I can't see how that can
possibly be a good idea.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company