> > > 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 se
> > 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
Thomas Lockhart writes:
> I'm sure this has been on the list, but I'm not recalling the
> explanation or workaround. My guess is that it is related to collation
> troubles with the new locale-always-enabled feature. I've tended to
> never enable this stuff in the past.
>
> The first symptom is fa
