Re: trouble with to_char('L')

From: Mikko <mhannesy(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: trouble with to_char('L')
Date: 2009-04-21 20:32:18
Message-ID: 40c6d9160904211332i73e44103s375f45fc46af77da@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Tue, Apr 21, 2009 at 8:13 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Maybe the problem here is that the chosen locales are not UTF8.  Does it
> work if you set lc_numeric and lc_monetary to "Finnish_Finland.65001"
> instead?  Those should match the server_encoding.

alter database testdb set lc_monetary(or numeric) to
'Finnish_Finland.65001' returns:
ERROR: invalid value for parameter "lc_monetary": "Finnish_Finland.65001"

However, I noticed that both lc_collate and lc_ctype are set to
Finnish_Finland.1252 by the installer. Should I have just run initdb
with --locale fi_FI.UTF8 at the very start? The to_char('L') works
fine with a database with win1252 encoding.

Mikko

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-04-21 20:36:21 Re: Yet another "drop table vs delete" question
Previous Message Christophe 2009-04-21 20:32:02 Re: Yet another "drop table vs delete" question

Browse pgsql-hackers by date

  From Date Subject
Next Message steven king 2009-04-21 20:48:13 Re: Automating Partitions in PostgreSQL - Query on syntax
Previous Message Heikki Linnakangas 2009-04-21 19:27:59 Re: New trigger option of pg_standby