Thread

1. BUG #1344: Locale problem

   PostgreSQL Bugs List <pgsql-bugs@postgresql.org> — 2004-12-07T10:20:22Z

   The following bug has been logged online:
   
   Bug reference:      1344
   Logged by:          Jan Kralji
   
   Email address:      jan@patware.si
   
   PostgreSQL version: 7.4.6
   
   Operating system:   Linux Debian
   
   Description:        Locale problem
   
   Details: 
   
   I cannot start postgres because unknow error. In log i can get this: 
   FATAL:  XX000: failed to initialize lc_messages to ""
   LOCATION:  InitializeGUCOptions, guc.c:1867
   ------------------------------------------------
   locale returns me this 
   ...
   LC_MESSAGES="sl_SI"
   ...
   -------------------------------------------------
   By default i set locale to sl_SI.iso88592
   
   What to do?
   
   
   

2. Re: BUG #1344: Locale problem

   Tom Lane <tgl@sss.pgh.pa.us> — 2004-12-07T15:25:51Z

   "PostgreSQL Bugs List" <pgsql-bugs@postgresql.org> writes:
   > I cannot start postgres because unknow error. In log i can get this: 
   > FATAL:  XX000: failed to initialize lc_messages to ""
   
   Are you sure that your LC_MESSAGES setting is compatible with the active
   LC_CTYPE setting?  I'm not certain about this, but I think that some
   platforms may reject the setlocale call if LC_MESSAGES implies a
   different encoding (eg, utf8 vs latin-n) than LC_CTYPE does.
   
   			regards, tom lane