| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Server-side support of all encodings |
| Date: | 2007-04-15 11:09:42 |
| Message-ID: | 20070415.200942.119856171.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Tatsuo Ishii <ishii(at)postgresql(dot)org> 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
Done.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-04-15 11:56:39 | Re: Wishlist updates |
| Previous Message | Steve | 2007-04-15 08:13:53 | Re: [HACKERS] choose_bitmap_and again (was Re: [PERFORM] Strangely Variable Query Performance) |