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

• Re: trouble with to_char('L') at 2009-04-21 17:13:38 from Alvaro Herrera

Responses

• Re: trouble with to_char('L') at 2009-04-21 23:13:22 from Alvaro Herrera

pgsql-hackers by date

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

pgsql-general by date

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