Jim Nasby <jim.na...@bluetreble.com> writes: > On 1/6/17 2:45 PM, Tom Lane wrote: >> While I was checking the patch to verify that it didn't change any >> behavior, I noticed that it did, and there's a pre-existing bug here: >> pltcl_build_tuple_result is applying utf_e2u to the Tcl_GetString results, >> but surely that should be utf_u2e instead. Fortunately we haven't shipped >> this code yet.
> Ugh. > For this patch lets just fix that (see attached). I already fixed it in HEAD. > Moving forward, I think it'd be good to improve this... Yeah, it's pretty ugly, but I'm not sure what would be a better design. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers