On Tue, May 06, 2003 at 11:34:19PM -0400, Tom Lane wrote:
> random junk is in initdb's environment. Perhaps "initdb --use-locale"
> should be required to get the current behavior?
Yes. From the point of view of an administrator, the current
behaviour is the worst possible one, because you can find yourself
with a real database before you realise what's happened. Then you
need to do initdb to recover.
What's worse, it's not obvious from looking at the encoding of the
database what the problem might be. If you know about this, of
course, then you know what to do. But someone inexperienced with
Postgres (who, for instance, is a new developer working on, say, a
registry database ;-) might easily spend quite a bit of time fooling
around with optimisations trying to fix a problem which wouldn't be
there if only the locale had been set correctly.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew@libertyrms.info> M2P 2A8 +1 416 646 3304
x110
