Re: Testing 9.2 in ~production environment
От | James Cloos |
---|---|
Тема | Re: Testing 9.2 in ~production environment |
Дата | |
Msg-id | m38vfkjnaz.fsf@carbon.jhcloos.org обсуждение исходный текст |
Ответ на | Re: Testing 9.2 in ~production environment (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Testing 9.2 in ~production environment
|
Список | pgsql-hackers |
>>>>> "JB" == Josh Berkus <josh@agliodbs.com> writes: JB> Can you check the collations of the two databases? I'm wondering if 9.1 JB> is in "C" collation and 9.2 is something else. Thanks! pg_dump -C tells me these two differences: -SET client_encoding = 'SQL_ASCII';+SET client_encoding = 'UTF8'; -CREATE DATABASE dbm WITH TEMPLATE = template0 ENCODING = 'SQL_ASCII' LC_COLLATE = 'C' LC_CTYPE = 'C';+CREATE DATABASE dbmWITH TEMPLATE = template0 ENCODING = 'UTF8' LC_COLLATE = 'C' LC_CTYPE = 'en_US.UTF-8'; for every db in the clusters. I presume that lc_ctype is the significant difference? LC_CTYPE *is* specified as 'C' in the dump from which I created the 9.2 cluster, so it must have been overridden by pg_restore. I see that my dist's /etc rc script now sets LC_CTYPE. Would that explain why lc_ctype changed between the two clusters? Is there any way to alter a db's lc_ctype w/o dumping and restoring? I want to preserve some of the changes made since I copied the 9.1 cluster. Alter database reports that lc_ctype cannot be changed. -JimC -- James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
В списке pgsql-hackers по дате отправления: