Andrew Dunstan <[email protected]> writes: > Perhaps I expressed myself badly. What I meant was that we should keep > the json and text escape rules in sync, as they are now. Since we're > changing the text rules to allow resolvable non-ascii unicode escapes > in non-utf8 locales, we should do the same for json.
Got it. I'll make the patch do that in a little bit.
regards, tom lane
