pg_regress multibyte -> encoding?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_regress multibyte -> encoding?
Date: 2011-04-13 19:02:30
Message-ID: 1302721350.11858.6.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-04-13 19:30:06 Re: [PATCH] Fix that NOSUPERUSER implies REPLICATION unless specified contrarily
Previous Message Bruce Momjian 2011-04-13 15:34:55 Fix for pg_upgrade