> > > The first symptom is failures in the char regression test...
> > initdb --no-locale
> Ooh. Thanks, that fixes it. Where would I have found this in the docs? I
> was looking in the wrong place (in configure/build) rather than at
> initdb. Should we have something in the release notes? I see (now that I
> look) that there is a one-liner, but istm that this may deserve a
> paragraph in the "significant changes" category.
Since once a user do initdb without knowing he is enabling the locale
support, the only way to recover from it is doing initdb again. I
suggest something like showing a message in the initdb time
emphasizing he is enabling the local support.
In response to
pgsql-hackers by date
|Next:||From: Nicolas Bazin||Date: 2002-04-22 02:00:09|
|Subject: How to know whether a table is locked ?|
|Previous:||From: Thomas Lockhart||Date: 2002-04-22 00:06:28|
|Subject: Re: GUC vs variable.c (was Patches applied...)|