postgresql-8.3 cluster locale should not be utf8
Bug #207779 reported by
Torsten Krah
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-common (Debian) |
Fix Released
|
Unknown
|
|||
postgresql-common (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
Binary package hint: postgresql-8.3
On Gutsy, the initdb command runs with locale=utf8.
I don't hesitate using utf8, but it prevents you from using any other charsets which are not compatible (e.g. latin1).
I think it would be better to use C or POSIX locale and as default encoding utf8, so you are still able to use other charsets than utf8 (initdb --locale=POSIX -E UTF8 ...)
Torsten
Changed in postgresql-common: | |
status: | Unknown → Fix Released |
To post a comment you must log in.
IMHO UTF-8 is absolutely the right thing nowadays. But even if you do not like it, you are welcome to pg_dropcluster the existing instance, and create a new one (man pg_createcluster) using a different default encoding. Or just create a new database with a different encoding.
What do you mean with "prevents you from using other charsets"?