Re: [HACKERS] pg_regress multibyte -> encoding?

2011-04-13 Thread Tom Lane
Peter Eisentraut  writes:
> 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?

+1

> Does anyone use the old interface?  Do we need to keep it?

As long as this is only in HEAD and not back-patched, I don't see a need
for that.

regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


[HACKERS] pg_regress multibyte -> encoding?

2011-04-13 Thread Peter Eisentraut
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?



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers