On Sat, 2009-10-03 at 12:20 -0400, Tom Lane wrote: > I am inclined to think that we should add another expected-file > showing the single-byte \200 result. What that might get displayed > as on the local system isn't really our concern.
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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
