Re: Some 8.4 changes needed according to pg_migrator testing
От | Peter Eisentraut |
---|---|
Тема | Re: Some 8.4 changes needed according to pg_migrator testing |
Дата | |
Msg-id | 200905082034.26241.peter_e@gmx.net обсуждение исходный текст |
Ответ на | Re: Some 8.4 changes needed according to pg_migrator testing (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: Some 8.4 changes needed according to pg_migrator testing
|
Список | pgsql-hackers |
On Friday 08 May 2009 19:09:51 Heikki Linnakangas wrote: > How about only outputting the LC_COLLATE/CTYPE options for databases > that use a non-default setting? In the common scenarios where you have > the same collation for the whole cluster it would work just like in > previous releases. If you dump and restore a database with default > locale to a cluster initialized with a different locale, the database is > restored with the default locale of the target cluster. But if you > explicitly set a database to use a different locale, that would be > preserved in dumps with the caveat that you'd have to change it manually > if you restore to a cluster on a different platform. That was my latest thinking as well. And it preserves the not-uncommon use case that you pg_dumpall and restore your database after having initdb'ed with a different locale/encoding in order to, say, switch to Unicode.
В списке pgsql-hackers по дате отправления: