Message-ID: <56997E54.9030109@anastigmatix.net> Date: Fri, 15 Jan 2016 18:18:44 -0500 From: Chapman Flack MIME-Version: 1.0 References: <56945E0E.3000104@hogranch.com> <56945EA8.9090505@anastigmatix.net> <56946D05.9050508@anastigmatix.net> <5698E79E.6040904@hogranch.com> <56990F46.2000309@anastigmatix.net> <569948F9.9030603@hogranch.com> <56994A59.9050000@anastigmatix.net> <569978AA.9030207@hogranch.com> In-Reply-To: <569978AA.9030207@hogranch.com> Subject: Re: [Pljava-dev] built, now how to install? Content-Type: text/plain; charset="us-ascii" On 01/15/16 17:54, John R Pierce wrote: > I note there's a almost 1 second delay between that CONTEXT and that ERROR, > suggesting the error is NOT in that CREATE OR REPLACE FUNCTION. Ah, I feel better now. That would be the unicode roundtrip test ... it does have roughly a million Unicode codepoints to check. (That wouldn't take nearly a second, unless you wrote it in, say, SQL with CTEs, and then it would. :) If you set log_error_verbosity to verbose, you'll see the LOCATION is the chr function, which is used in the Unicode test. That's actually illustrating a strange PostgreSQL quirk ... even though in general the encodings are all about interconvertible subsets of Unicode (with SQL_ASCII being the only weird, undefinable one) ... the chr function (and U'' strings) are only fully usable in UTF8, period ... and crippled /in every other encoding/. I've never asked why.... Since that code is just a regression test, I should just change it to be skipped unless the server is using UTF8. -Chap _______________________________________________ Pljava-dev mailing list Pljava-dev@lists.pgfoundry.org http://lists.pgfoundry.org/mailman/listinfo/pljava-dev