| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
| Cc: | 'Heikki Linnakangas' <hlinnaka(at)iki(dot)fi>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Deprecate custom encoding conversions |
| Date: | 2020-12-03 01:50:40 |
| Message-ID: | X8hEcANYNmVthMEq@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 03, 2020 at 12:54:56AM +0000, tsunakawa(dot)takay(at)fujitsu(dot)com wrote:
> I can't answer deeper questions because I'm not familiar with
> character sets, but I saw some Japanese web articles that use CREATE
> CONVERSION to handle external characters. So, I think we may as
> well retain it. (OTOH, I'm wondering how other DBMSs support
> external characters and what Postgres should implement it.)
Tsunakawa-san, could you post a link to this article, if possible? I
am curious about their problem and why they used CREATE CONVERSION as
a way to solve it. That's fine even if it is in Japanese.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hou, Zhijie | 2020-12-03 01:54:33 | RE: A new function to wait for the backend exit after termination |
| Previous Message | Tom Lane | 2020-12-03 01:47:35 | Re: Deprecate custom encoding conversions |