Re: Getting the red out (of the buildfarm) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Getting the red out (of the buildfarm)
Date
Msg-id 2844.1254591650@sss.pgh.pa.us
Whole thread Raw
In response to Re: Getting the red out (of the buildfarm)  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Getting the red out (of the buildfarm)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> OK, the reason I couldn't reproduce this for the life of me is that I
> had PGCLIENTENCODING=UTF8 in the environment of the server(!).  Once I
> unset that, I could reproduce the problem.  This could be made a bit
> more well-defined if we ran pg_regress with --multibyte=something,
> although that is then liable to fail in encodings that don't have an
> equivalent of \u0080.  Some with your suggestion above: It will only
> work for some encodings.

I'm back to wondering why we need a regression test for this at all.
Wouldn't it be just as useful to be testing a character code that
is well-defined everywhere?  Or just drop this test altogether?
It's already got way too many expected files for my taste.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Getting the red out (of the buildfarm)
Next
From: Bruce Momjian
Date:
Subject: Re: Use "samehost" by default in pg_hba.conf?