Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: New to PostgreSQL, performance considerations


  • 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: Mon, 11 Dec 2006 11:11:29 +0900
  • Message-id: <12DF97AF-3B52-4955-9A35-46D2B0255F32(at)seespotcode(dot)net>


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





Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group