Postgres Pro
Downloads
Home   >   mailing lists

Thread: encoding warnings while intializing database.

encoding warnings while intializing database.

From
Wes Sheldahl
Date:
Hi,

I'm dutifully reporting some warnings I received when initializing a
postgresql database.
The command I ran was this:
sudo -u postgres /opt/local/lib/postgresql84/bin/initdb -E UTF-8 -D
/opt/local/var/db/postgresql84/defaultdb

(I had tried before without the '-E UTF-8' option, but that failed
completely with an encoding-related error.)

This is OSX 10.4 (Tiger); postgresql version 8.4, installed via macports.

here's the relevant part of the output:

initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... WARNING:  could not determine
encoding for locale "en_US.US-ASCII": codeset is "US-ASCII"
DETAIL:  Please report this to <pgsql-bugs@postgresql.org>.
WARNING:  could not determine encoding for locale "en_US.US-ASCII":
codeset is "US-ASCII"
DETAIL:  Please report this to <pgsql-bugs@postgresql.org>.
ok
copying template1 to postgres ... WARNING:  could not determine
encoding for locale "en_US.US-ASCII": codeset is "US-ASCII"
DETAIL:  Please report this to <pgsql-bugs@postgresql.org>.
WARNING:  could not determine encoding for locale "en_US.US-ASCII":
codeset is "US-ASCII"
DETAIL:  Please report this to <pgsql-bugs@postgresql.org>.
ok


Otherwise, postgresql appears to be up and running. Thanks,

--
Wes Sheldahl
wes.sheldahl@gmail.com

Re: encoding warnings while intializing database.

From
Tom Lane
Date:
Wes Sheldahl <wes.sheldahl@gmail.com> writes:
> copying template1 to template0 ... WARNING:  could not determine
> encoding for locale "en_US.US-ASCII": codeset is "US-ASCII"
> DETAIL:  Please report this to <pgsql-bugs@postgresql.org>.

Thanks for the report.  We have already modified CVS HEAD to default
to SQL_ASCII in this situation, though the actual usefulness of that
behavior is a bit debatable.  You'd probably be better off selecting
one of the locale values with a more explicit codeset setting,
such as en_US.ISO8859-1 or en_US.UTF-8.

            regards, tom lane