> > > 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. -- Tatsuo Ishii ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
