initdb in 8.3 - Mailing list pgsql-general

From Tim Tassonis
Subject initdb in 8.3
Date
Msg-id 480F057B.6060801@cubic.ch
Whole thread Raw
Responses Re: initdb in 8.3  (Richard Huxton <dev@archonet.com>)
Re: initdb in 8.3  (Peter Eisentraut <peter_e@gmx.net>)
Re: initdb in 8.3  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
List pgsql-general
Hi

I just recently compiled and installed 8.3.1 on a System that has UTF-8
as the default characterset in the environment. Copied the binaries, run
initdb without parameters, the usual stuff.

As you probably are all aware of, this results now in a cluster that
will only allow you to create UTF-8 databases. I have read some posts
regarding this topic where it is explained that allowing LATIN1 on a
cluster initialized with UTF-8 will give you problems anyway etc and you
have to use locale=C to be able to create databases with different
charactersets.

My question is: Why then is --locale=C not the default for initdb, as I
do regard it as a rather big annoyance that a default installation on
probably almost any modern linux distribution results in a UTF-8 only
cluster, fixable only by dropping all databases, rerun initdb and the
reimporting them again.

Apart from that I'd of course like to restate that postgresql is a
wonderful software which I like very much.

Bye
Tim



pgsql-general by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Debian etch, backport postgresql 8.3 experiences?
Next
From: Andreas 'ads' Scherbaum
Date:
Subject: Re: How to modify ENUM datatypes?