| From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_regress multibyte setting |
| Date: | 2011-01-13 02:52:47 |
| Message-ID: | AANLkTikKDFZzuc2Q0BHeYoZhh7dm_9o-kT+96VN8W8F=@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 12, 2011 at 08:06, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Is it a good idea that we run make check with MULTIBYTE = SQL_ASCII by
> default? We run it with the user's locale by default, so shouldn't we
> use the encoding that belongs to the locale by default? Otherwise we
> are testing a fairly unrepresentative environment. If you really want
> to test SQL_ASCII you could of course choose it explicitly or set the
> locale to C.
It seems good to run make check successfully on many platforms,
but we might miss locale-dependent bugs.
Personally speaking, I often recommend to use UTF-8 + C locale combinations
for users, but I'm not sure it's the most common use-cases or not.
--
Itagaki Takahiro
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-01-13 03:05:53 | Re: Database file copy |
| Previous Message | Anthony Gentile | 2011-01-13 02:37:42 | N-grams |