From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Martin Pitt <martin(at)piware(dot)de> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Recommended approach for upgrading DBs with nonmatching encodings |
Date: | 2008-03-31 06:38:51 |
Message-ID: | 14483.1206945531@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Martin Pitt <martin(at)piware(dot)de> writes:
> BTW, many people seem to run the server under C and use different
> encodings in their DBs (latin, UTF8). Shouldn't that cause similar
> problems with collation, data type checking (ischar(), etc.)? What do
> you recommend should the upgrade script do if it encounters an 8.[12]
> server running under C?
Yeah, C locale will work with any encoding, for small values of "work"
--- one problem is that you get byte-by-byte sorting which doesn't act
all that sensibly in a lot of encodings, and another is that
upper()/lower() only work for the base ASCII letters.
I gather that this behavior is just fine with a lot of the Far Eastern
contingent, though you'd have to ask them for details. In any case
you should not second-guess such a configuration during upgrade.
People do use it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Marcello Ceschia | 2008-03-31 12:26:54 | BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data |
Previous Message | Martin Pitt | 2008-03-31 06:22:49 | Re: Recommended approach for upgrading DBs with nonmatching encodings |