pg_regress multibyte -> encoding? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject pg_regress multibyte -> encoding?
Date
Msg-id 1302721350.11858.6.camel@vanquo.pezone.net
Whole thread Raw
Responses Re: pg_regress multibyte -> encoding?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
pg_regress supports a --multibyte option, which can also be invoked
using the MULTIBYTE make variable when you run make check.  I think this
is fairly unknown, but we are now documenting it as part of how to run
the collation regression tests.  I think it would also be useful in the
PL/Python regression tests for some of the unicode test variants.

So before this spreads too widely, should we rename it to --encoding and
ENCODING to be consistent with the naming everywhere else?  Does anyone
use the old interface?  Do we need to keep it?




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Fix for pg_upgrade
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] Fix that NOSUPERUSER implies REPLICATION unless specified contrarily