> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> >> I think the best way to proceed is probably to fix this in HEAD but
> >> not back-patch it.  During a dump and reload the encoding can be
> >> corrected to something safe.
> > Ok. Shall I go ahead and remove JOHAB in HEAD?
> +1 for me.
>                       regards, tom lane


BTW, do we have to modify pg_dump or pg_restore so that it can
automatically adjust JOHAB to UTF8 (it's the only safe encoding
compatible with JOHAB)? I'm not sure it's worth the trouble. Maybe
documenting in the release note is enough? I guess that there is 0
users who are using JOHAB.
Tatsuo Ishii
SRA OSS, Inc. Japan

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to