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 compatibility or search for
a compatible encoding ... without that algorithm the whole thing's moot.

BTW, what happens if there is more than one apparently-matching
encoding?  (It might be best to error out in this case, on the theory
that we evidently don't have a correct matching.)

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Reply via email to