Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Now I wonder why there are client-only encodings at all.
Backend encodings must follow the rule that non-first bytes of multibyte
sequences must have the high bit set, so that they cannot be mistaken
for ASCII characters. We allow client encodings to break that rule
though. (If you look at psql's lexical processing you will see the cost
we pay for that, and why I don't want to relax the rule in the backend.)
The encodings that break this rule are some multibyte Far Eastern
encodings (I forget which, but Tatsuo would know). There is certainly
no reason that any single-byte ASCII-superset encoding couldn't be
supported in the backend.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
