|From:||"Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>|
|To:||'Tatsuo Ishii' <ishii(at)sraoss(dot)co(dot)jp>|
|Subject:||Re: Supporting SJIS as a database encoding|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Tatsuo Ishii
> > But what I'm wondering is why PostgreSQL doesn't support SJIS. Was there
> any technical difficulty? Is there anything you are worried about if adding
> Yes, there's a technical difficulty with backend code. In many places it
> is assumed that any string is "ASCII compatible", which means no ASCII
> character is used as a part of multi byte string. Here is such a random
> example from src/backend/util/adt/varlena.c:
> /* Else, it's the traditional escaped style */
> for (bc = 0, tp = inputText; *tp != '\0'; bc++)
> if (tp != '\\')
> Sometimes SJIS uses '\' as the second byte of it.
Thanks, I'll try to understand the seriousness of the problem as I don't have good knowledge of character sets. But your example seems to be telling everything about the difficulty...
Before digging into the problem, could you share your impression on whether PostgreSQL can support SJIS? Would it be hopeless? Can't we find any direction to go? Can I find relevant source code by searching specific words like "ASCII", "HIGH_BIT", "\\" etc?
|Next Message||Michael Paquier||2016-09-05 08:01:42||Re: pg_basebackup stream xlog to tar|
|Previous Message||Tatsuo Ishii||2016-09-05 07:38:54||Re: Supporting SJIS as a database encoding|