Re: Getting the red out (of the buildfarm)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Getting the red out (of the buildfarm)
Date: 2009-10-03 17:40:50
Message-ID: 2844.1254591650@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-10-03 23:11:32 Re: Use "samehost" by default in pg_hba.conf?
Previous Message Peter Eisentraut 2009-10-03 17:37:37 Re: Getting the red out (of the buildfarm)