On Tue, Nov 23, 2010 at 5:51 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > The case I was worried about is dumping from one database and reloading > into another one with a different locale. Although I suppose there are > enough *other* reasons why that might fail that adding changes of > downcasing behavior might not be a big deal.
If you dump the whole database then pg_dump would create the new database with the correct encoding and locale. If you change it then that can already cause it to fail if the data can't be converted to the new encoding. And as you point out there are all kinds of ways you can cause that to fail by making the context incompatible with the definitions you're loading. The lesson we learned in the past is that we have to ignore the locale for all the characters present in the standard identifiers. Beyond that I think this is just an implementation problem which may be a show stopper in itself but if we can do anything with mulitbyte characters it's probably an improvement over what we do now. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
