Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 29F3E9FA162 for ; Sun, 10 Dec 2006 22:11:40 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 75096-03 for ; Sun, 10 Dec 2006 22:11:35 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from proton.planetargon.com (unknown [198.145.37.35]) by postgresql.org (Postfix) with ESMTP id 5D9FC9F9F75 for ; Sun, 10 Dec 2006 22:11:35 -0400 (AST) Received: from [172.16.1.106] (unknown [61.197.227.146]) by proton.planetargon.com (Postfix) with ESMTP id 043CA828131; Sun, 10 Dec 2006 18:11:32 -0800 (PST) In-Reply-To: <8a0c7af10612101747j33b09ddft21d3341cc95dfaf5@mail.gmail.com> References: <8a0c7af10612101141n2c7727c3r2f92345753960808@mail.gmail.com> <430d92a20612101336r3de8862coe618277fccb4006a@mail.gmail.com> <8a0c7af10612101702i49b5a533v4a2300d90d9dae6b@mail.gmail.com> <430d92a20612101718o239dbf9dg990e784c17bf175a@mail.gmail.com> <8a0c7af10612101747j33b09ddft21d3341cc95dfaf5@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <12DF97AF-3B52-4955-9A35-46D2B0255F32@seespotcode.net> Cc: pgsql-performance@postgresql.org Content-Transfer-Encoding: 7bit From: Michael Glaesemann Subject: Re: New to PostgreSQL, performance considerations Date: Mon, 11 Dec 2006 11:11:29 +0900 To: "Daniel van Ham Colchete" X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/196 X-Sequence-Number: 22252 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