Re: Why are there client-only encodings? - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Why are there client-only encodings?
Date
Msg-id 20040914.175957.35012679.t-ishii@sra.co.jp
Whole thread Raw
In response to Why are there client-only encodings?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
> I wanted to allow WIN1250 as a server-side encoding, in light of the 
> Windows port.  Now I wonder why there are client-only encodings at all.  
> Without knowing details, it seems the client-only encodings are all 
> "Windows world" encodings.  So was the original reason not to allow 
> these as server encodings that the server doesn't run on Windows?  If 
> so, should the category client-only encodings be abolished?

I think it's not just possible for some multi-byte encodings such as
SJIS(Shift-JIS) and Big5. Currently PostgreSQL will not accept them
because of they include special ASCII characters such as back slashes.
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: strk
Date:
Subject: gist cost estimator failing
Next
From: Philip Warner
Date:
Subject: Re: pg_restore segfault with pg-CVS