> Peter Eisentraut <peter_e@gmx.net> writes:
> > Tom Lane writes:
> >> We now have defenses against running a non-LOCALE-enabled backend in a
> >> database that was created in non-C locale. Shouldn't we likewise
> >> prevent a non-MULTIBYTE-enabled backend from running in a database with
> >> a multibyte encoding that's not SQL_ASCII? Or am I missing a reason why
> >> that is safe?
>
> > Not all multibyte encodings are actually "multi"-byte, e.g., LATIN2. In
> > that case the main benefit is the on-the-fly recoding between the client
> > and the server. If a non-MB server encounters that database it should
> > still work.
>
> Are these encodings all guaranteed to have the same collation order as
> SQL_ASCII?
Yes & no.
>If not, we have the same index corruption issues as for LOCALE.
If the backend is configued with LOCALE enabled and the database is
not configured with LOCALE, we will have a problem. But this will
happen with/without MUTIBYTE anyway. Mutibyte support does nothing
with LOCALE support.
--
Tatsuo Ishii
