From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_regress multibyte -> encoding? |
Date: | 2011-04-13 21:53:53 |
Message-ID: | 25764.1302731633@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:
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Brar Piening | 2011-04-13 22:14:00 | Re: Windows build issues |
Previous Message | Tom Lane | 2011-04-13 21:19:41 | GEQO-induced crash with provably dummy relations |