Thanks. I never intentionally changed the system locale but it is fixed now.
For those who are interested, this is how you do it. Change in
/etc/default/locale
the line
LANG="en_US.iso88591"
to
LANG="en_US.utf8"
and all new shells will automatically use this locale
--
You received this bug
Ah, that's what I thought. It's working as designed then, the psql
encoding defaults to the current locale's encoding; otherwise you could
not actually display non-ASCII characters from DB data.
Please note that Ubuntu does not officially support non-UTF8 locales, so
unless you have a strong reaso
postgres@hostname:~$ locale
LANG=en_US.iso88591
LANGUAGE=en_US:en
LC_CTYPE="en_US.iso88591"
LC_NUMERIC="en_US.iso88591"
LC_TIME="en_US.iso88591"
LC_COLLATE="en_US.iso88591"
LC_MONETARY="en_US.iso88591"
LC_MESSAGES="en_US.iso88591"
LC_PAPER="en_US.iso88591"
LC_NAME="en_US.iso88591"
LC_ADDRESS="en_US
Can you please copy&paste the output of "locale"?
** Changed in: postgresql-common (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: postgresql-common (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.lau
5 matches
Mail list logo