Re: Changeset Extraction v7.0 (was logical changeset generation)
От | Robert Haas |
---|---|
Тема | Re: Changeset Extraction v7.0 (was logical changeset generation) |
Дата | |
Msg-id | CA+Tgmob=C2wfYKH9C1ke9-t6PrQrENFv8AtoncHCrg4f+wKtdg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Changeset Extraction v7.0 (was logical changeset generation) (Craig Ringer <craig@2ndquadrant.com>) |
Ответы |
Re: Changeset Extraction v7.0 (was logical changeset generation)
Re: Changeset Extraction v7.0 (was logical changeset generation) Re: Changeset Extraction v7.0 (was logical changeset generation) |
Список | pgsql-hackers |
On Thu, Jan 16, 2014 at 10:15 PM, Craig Ringer <craig@2ndquadrant.com> wrote: > Anybody who actually uses SHIFT_JIS as an operational encoding, rather > than as an input/output encoding, is into pain and suffering. Personally > I'd be quite happy to see it supported as client_encoding, but forbidden > as a server-side encoding. That's not the case right now - so since we > support it, we'd better guard against its quirks. I think that *is* the case right now. pg_wchar.h sayeth: /* followings are for client encoding only */ PG_SJIS, /* Shift JIS (Winindows-932) */ PG_BIG5, /* Big5 (Windows-950) */ PG_GBK, /* GBK (Windows-936) */ -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: