Skip site navigation (1) Skip section navigation (2)

Re: Postgresql 9.0.4 initdb bug on solaris 64 bit

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gary Wong <gary_wong(at)dot(dot)ca(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Postgresql 9.0.4 initdb bug on solaris 64 bit
Date: 2011-06-15 14:05:17
Message-ID: 27318.1308146717@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Gary Wong <gary_wong(at)dot(dot)ca(dot)gov> writes:
> [Environment under in the postgres account]
> $ env
> LC_MONETARY=en_US.ISO8859-15
> LC_TIME=en_US.ISO8859-15
> LC_MESSAGES=C
> LC_CTYPE=en_US.ISO8859-1
> LC_COLLATE=en_US.ISO8859-15
> LC_NUMERIC=en_US.ISO8859-15

> [Message I get when I run initdb]
> $ initdb -D /usr/local/pgsql/data
> The files belonging to this database system will be owned by user
> "postgres".
> This user must also own the server process.

> The database cluster will be initialized with locales
>   COLLATE:  en_US.ISO8859-15
>   CTYPE:    en_US.ISO8859-1
>   MESSAGES: C
>   MONETARY: en_US.ISO8859-15
>   NUMERIC:  en_US.ISO8859-15
>   TIME:     en_US.ISO8859-15
> The default database encoding has accordingly been set to LATIN1.
> initdb: encoding mismatch
> The encoding you selected (LATIN1) and the encoding that the
> selected locale uses (LATIN9) do not match.  This would lead to
> misbehavior in various character string processing functions.
> Rerun initdb and either do not specify an encoding explicitly,
> or choose a matching combination.

This is not a bug.  You've got inconsistent environment settings,
and the error message seems reasonably appropriate for that.
Try making LC_CTYPE match the rest.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2011-06-15 15:16:35
Subject: Re: [GENERAL] psql \s not working - OS X
Previous:From: YannDate: 2011-06-15 13:00:40
Subject: BUG #6061: Progresql.exe memory usage using HOLD cursor.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group