| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | "Daniel van Ham Colchete" <daniel(dot)colchete(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: New to PostgreSQL, performance considerations |
| Date: | 2006-12-11 02:11:29 |
| Message-ID: | 12DF97AF-3B52-4955-9A35-46D2B0255F32@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Dec 11, 2006, at 10:47 , Daniel van Ham Colchete wrote:
> I never understood what's the matter between the ASCII/ISO-8859-1/UTF8
> charsets to a database.
If what you mean by ASCII is SQL_ASCII, then there is at least one
significant difference between UTF8 (the PostgreSQL encoding) and
SQL_ASCII. AIUI, SQL_ASCII does no checking at all with respect to
what bytes are going in, while UTF8 does make sure to the best of its
ability that the bytes represent valid UTF-8 characters, throwing an
error if an invalid byte sequence is detected.
There's more information regarding this here:
http://www.postgresql.org/docs/8.2/interactive/
multibyte.html#MULTIBYTE-CHARSET-SUPPORTED
Michael Glaesemann
grzm seespotcode net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Stone | 2006-12-11 02:18:49 | Re: New to PostgreSQL, performance considerations |
| Previous Message | Daniel van Ham Colchete | 2006-12-11 01:47:01 | Re: New to PostgreSQL, performance considerations |