I wrote:
I've worked out a scheme that should adequately detect encoding
mismatches in initdb.
Done.
Karel pointed me to some other projects that are trying to do the same
thing, and they are no smarter than what we have now.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
I've worked out a scheme that should adequately detect encoding
mismatches in initdb. Please comment on the following behavior.
The locale is still taken from the environment or the command line; no
change.
If the locale is C or POSIX, then we set the encoding to SQL_ASCII or
whatever was
Tom Lane wrote:
The behavioral description sounds fine, but I was eagerly awaiting
your description of exactly how you'd test for compatibility or
search for a compatible encoding ... without that algorithm the whole
thing's moot.
It's just an explicit list of things that spell similarly.
Peter Eisentraut [EMAIL PROTECTED] writes:
I've worked out a scheme that should adequately detect encoding
mismatches in initdb. Please comment on the following behavior.
The behavioral description sounds fine, but I was eagerly awaiting your
description of exactly how you'd test for
