RE: Deprecate custom encoding conversions

From: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>
To: '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 02:48:13
Message-ID: TYAPR01MB29903E5C4A86C3CC5065A541FEF20@TYAPR01MB2990.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards
Takayuki Tsunakawa

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message osumi.takamichi@fujitsu.com 2020-12-03 03:14:52 RE: Disable WAL logging to speed up data loading
Previous Message Kasahara Tatsuhito 2020-12-03 02:46:09 Re: autovac issue with large number of tables