Re: Deprecate custom encoding conversions

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>, 'Michael Paquier' <michael(at)paquier(dot)xyz>
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 03:57:35
Message-ID: 4b8971dc-a7e2-19c1-2e58-046881f2e276@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020/12/03 11:48, tsunakawa(dot)takay(at)fujitsu(dot)com wrote:
> From: Michael Paquier <michael(at)paquier(dot)xyz>
>> 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.
>
> I just pulled info from my old memory in my previous mail. Now the following links seem to be relevant. (They should be different from what I saw in the past.)
>
> https://ml.postgresql.jp/pipermail/pgsql-jp/2007-January/013103.html
>
> https://teratail.com/questions/295988
>
> IIRC, the open source Postgres extension EUDC also uses CREATE CONVERSION.

FWIW, about four years before, for the real project, I wrote
the extension [1] that provides yet another encoding conversion
from UTF-8 to EUC_JP, to handle some external characters.
This extension uses CREATE CONVERSION.

[1]
https://github.com/MasaoFujii/pg_fallback_utf8_to_euc_jp

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-12-03 03:58:45 Re: Deprecate custom encoding conversions
Previous Message Bharath Rupireddy 2020-12-03 03:56:08 Re: A new function to wait for the backend exit after termination