"Iuri Sampaio" <[EMAIL PROTECTED]> writes:
> I don;t understand how it's related with postgresql installation. I never
> had this problem before.
> My locale is set:
> debian:~# locale -a
> C
> en_US.utf8
> POSIX
Well, your original report was about this:
FATAL: invalid value for parameter "lc_messages": "en_CA.UTF-8"
which evidently is not a locale that your system has got. The
locale -a printout suggests that if it is there, it'd be named
"en_CA.utf8", and it's hard to tell whether your platform would
be forgiving of the spelling difference or not. In any case,
the question is where Postgres got that setting from. AFAIK
the only likely explanation is that LANG was set that way when
you ran initdb.
You could try modifying lc_messages in postgresql.conf, but it
might be safer to wipe the database directory and re-initdb
with a corrected LANG setting.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
