Re: Retiring some encodings? - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Retiring some encodings?
Date
Msg-id 20250606.085056.525174573937784302.ishii@postgresql.org
Whole thread Raw
In response to Re: Retiring some encodings?  (Christoph Berg <myon@debian.org>)
List pgsql-hackers
>> Agreed that the so-said "state" level requirement would be a
>> non-starter.
> 
> Or maybe support for using these as server encodings could be
> removed, keeping the client_encoding part intact?

GB18030 is already client encoding only, and cannot be used as a
server encoding. The only way to save GB18030 data into database is,
converting GB18030 to UTF-8 (which can be done automatically).

Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Non-reproducible AIO failure
Next
From: Andres Freund
Date:
Subject: We should lazy-initialize the deadlock checker state memory