Re: trouble with to_char('L')

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Mikko <mhannesy(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: trouble with to_char('L')
Date: 2009-04-21 23:13:22
Message-ID: 20090421231322.GV10358@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Mikko escribió:
> 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"

Ouch ... I thought that was the way that Windows designated UTF8
locales, but maybe I am wrong.

> 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.

Hmm, it should have disallowed the creation of an UTF8 database then.
Maybe that part is what is broken here.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Crowe, Eric 2009-04-21 23:43:33 Can Autovaccuum also reindex
Previous Message Jeff Davis 2009-04-21 21:59:02 Re: Yet another "drop table vs delete" question

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-04-21 23:38:21 Re: [ADMIN] License Issue
Previous Message Adriano Lange 2009-04-21 23:04:43 RelOptInfo cache