Skip site navigation (1) Skip section navigation (2)

Re: How to extend server side encoding GBK

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Xiong He <iihero(at)qq(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: How to extend server side encoding GBK
Date: 2012-07-02 15:10:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"=?ISO-8859-1?B?WGlvbmcgSGU=?=" <iihero(at)qq(dot)com> writes:
> I just noticed that PG not support the following encoding: 
> 	/* followings are for client encoding only */
> 	PG_SJIS,					/* Shift JIS (Winindows-932) */
> 	PG_BIG5,					/* Big5 (Windows-950) */
> 	PG_GBK,						/* GBK (Windows-936) */
> 	PG_UHC,						/* UHC (Windows-949) */
> 	PG_GB18030,					/* GB18030 */
> 	PG_JOHAB,					/* EUC for Korean JOHAB */
> 	PG_SHIFT_JIS_2004,			/* Shift-JIS-2004 */
> 	_PG_LAST_ENCODING_			/* mark only */

> But  PG_GBK and PG_GB18030 are very popular in Chinese charset.
> Could anybody give some hints about how to extend it in PG source code?

The reason those aren't supported is that they aren't strict ASCII
supersets, ie there are multibyte characters in which not all the bytes
have the high bit set.  This breaks string-processing assumptions all
over the place.  We are not going to accept any patch that tries to
change that, because it would be too complicated, fragile, and slow.

Is there a reason why it's not good enough to use these just on the
client side, with the server internally using utf8?

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Thom BrownDate: 2012-07-02 15:11:23
Subject: Re: Event Triggers reduced, v1
Previous:From: Tom LaneDate: 2012-07-02 15:06:16
Subject: Re: pgsql: Make walsender more responsive.

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group