Re: [ADMIN] locale problems
Hornyak Laszlo writes: I made a failure. I changed operating system under my database from Red Hat 8.0 to Debian 3.0 (Woody), without pg_dump-ing the database. The database version haven`t changed. Now I cannot start my database on the same data directory, it stops with the following failure: Failed to initialize lc_messages to '' FATAL: invalid value for option 'LC_MESSAGES': 'en_US.UTF-8' pg_ctl: cannot start postmaster Examine the log output. Install the en_US.UTF-8 locale on your system. Try dpkg-reconfigure locales. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 8: explain analyze is your friend
[ADMIN] locale problems
Hi all! I made a failure. I changed operating system under my database from Red Hat 8.0 to Debian 3.0 (Woody), without pg_dump-ing the database. The database version haven`t changed. Now I cannot start my database on the same data directory, it stops with the following failure: Failed to initialize lc_messages to '' FATAL: invalid value for option 'LC_MESSAGES': 'en_US.UTF-8' pg_ctl: cannot start postmaster Examine the log output. I tryed with modifying the postgresql.conf with a number of different locale settings but they did not work. What is the shortest way to get my database back? Should I install RedHat back? Thanks, Laszlo ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [ADMIN] locale problems
Cool :) Thanks, Laszlo On Thu, 7 Aug 2003, Peter Eisentraut wrote: Hornyak Laszlo writes: I made a failure. I changed operating system under my database from Red Hat 8.0 to Debian 3.0 (Woody), without pg_dump-ing the database. The database version haven`t changed. Now I cannot start my database on the same data directory, it stops with the following failure: Failed to initialize lc_messages to '' FATAL: invalid value for option 'LC_MESSAGES': 'en_US.UTF-8' pg_ctl: cannot start postmaster Examine the log output. Install the en_US.UTF-8 locale on your system. Try dpkg-reconfigure locales. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[ADMIN] Locale problems
Hello! I have a db cluster which contains databases with LATIN2 encoding and some databases with UNICODE encoding. If I initalise the cluster with --locale=sl_SI option, then special characters in LATIN2 databases are sorted correctly, but special chars in UNICODE dbs end up in wrong places; and the other way around if I use sl_SI.utf8 locale (or no locale). Is there a way to get correct sorting order in both cases, other than running two separate servers? ( pg 7.3.1 ) Thank you. Best regards, Aleksander ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
