From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] Add CANONICAL option to xmlserialize |
Date: | 2023-03-05 23:32:49 |
Message-ID: | CA+hUKG+y+qP9HLu9L0oGmMQ6P6_X7LREWoTtiDBLooBhuznTfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 6, 2023 at 11:20 AM Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> wrote:
> On 05.03.23 22:00, Thomas Munro wrote:
> > could be something to do with
> > our environment, since .cirrus.yml sets LANG=C in the 32 bit test run
> > -- maybe try that locally?
> Also using LANGUAGE=C the result is the same for me - all tests pass
> just fine.
I couldn't reproduce that locally either, but I just tested on CI with
your patch applied saw the failure, and then removed
"PYTHONCOERCECLOCALE=0 LANG=C" and it's all green:
https://github.com/macdice/postgres/commit/91999f5d13ac2df6f7237a301ed6cf73f2bb5b6d
Without looking too closely, my first guess would have been that this
just isn't going to work without UTF-8 database encoding, so you might
need to skip the test (see for example
src/test/regress/expected/unicode_1.out). It's annoying that "xml"
already has 3 expected variants... hmm. BTW shouldn't it be failing
in a more explicit way somewhere sooner if the database encoding is
not UTF-8, rather than getting confused?
From | Date | Subject | |
---|---|---|---|
Next Message | Soumyadeep Chakraborty | 2023-03-06 02:10:27 | pg_rewind: Skip log directory for file type check like pg_wal |
Previous Message | Thomas Munro | 2023-03-05 22:20:48 | Re: Refactor to introduce pg_strcoll(). |