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. -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
- [HACKERS] Shouldn't non-MULTIBYTE backend refuse to start... Tom Lane
- Re: [HACKERS] Shouldn't non-MULTIBYTE backend refuse... Peter Eisentraut
- Re: [HACKERS] Shouldn't non-MULTIBYTE backend re... Tom Lane
- Re: [HACKERS] Shouldn't non-MULTIBYTE backen... Tatsuo Ishii
- Re: [HACKERS] Shouldn't non-MULTIBYTE ba... Tom Lane
- Re: [HACKERS] Shouldn't non-MULTIBY... Tatsuo Ishii
- Re: [HACKERS] Shouldn't non-MUL... Tom Lane
- Re: [HACKERS] Shouldn't non... Tatsuo Ishii
- Re: [HACKERS] Shouldn't non... Tom Lane
- Re: [HACKERS] Shouldn't non... Peter Eisentraut
- Re: [HACKERS] Shouldn't non... Tatsuo Ishii
- Re: [HACKERS] Shouldn't non... Tom Lane