Re: Deprecate custom encoding conversions - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Deprecate custom encoding conversions
Date
Msg-id X8hEcANYNmVthMEq@paquier.xyz
Whole thread Raw
In response to RE: Deprecate custom encoding conversions  ("tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com>)
Responses RE: Deprecate custom encoding conversions
List pgsql-hackers
On Thu, Dec 03, 2020 at 12:54:56AM +0000, tsunakawa.takay@fujitsu.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

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Deprecate custom encoding conversions
Next
From: "Hou, Zhijie"
Date:
Subject: RE: A new function to wait for the backend exit after termination