| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
| Cc: | 本家pgsql-hackersについて日本語で議論するML <hackers-jp(at)ml(dot)postgresql(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [hackers-jp: 219] Re: postgresql-8.1.4文字セットサポート |
| Date: | 2006-07-28 14:09:57 |
| Message-ID: | 20177.1154095797@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Glaesemann <grzm(at)seespotcode(dot)net> writes:
> Just to confirm, it does look like there's a discrepancy between what
> is in the documentation and the actual behavior of the server. The
> documentation indicates that SJIS is a valid server encoding:
This is a documentation error --- SJIS is certainly not a valid server
encoding (it's not 8-bit-safe). Will fix --- thanks for pointing it out.
> createdb: database creation failed: ERROR: SJIS is not a valid
> encoding name
I wonder if it would be worth changing the code so that you get a
complaint saying the encoding is known but not allowed on the server
side. It hasn't come up before, so maybe it's not worth the trouble
... but this message seems a bit confusing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-28 14:11:32 | Re: GUC with units, details |
| Previous Message | Alvaro Herrera | 2006-07-28 14:03:31 | Re: [HACKERS] pgstattuple extension for indexes |