X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 337A85E46ED for ; Mon, 16 Aug 2004 12:04:41 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23026-10 for ; Mon, 16 Aug 2004 15:04:37 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id D0C2C5E46E8 for ; Mon, 16 Aug 2004 12:04:29 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i7GF4XOa013568; Mon, 16 Aug 2004 11:04:33 -0400 (EDT) To: Achilleus Mantzios Cc: pgsql-sql@postgresql.org Subject: Re: SQL_ASCII and UNICODE server_encoding In-reply-to: References: Comments: In-reply-to Achilleus Mantzios message dated "Mon, 16 Aug 2004 16:56:29 +0300" Date: Mon, 16 Aug 2004 11:04:33 -0400 Message-ID: <13567.1092668673@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/147 X-Sequence-Number: 18644 Achilleus Mantzios writes: > So if SQL_ASCII should be fine for UTF-8 storage. > (here i must have missed something, tho..), whats > the purpose of server_encoding=UNICODE? If you use SQL_ASCII, the server will *store* Unicode just fine, but it won't *know* it is Unicode. So if you just want raw data storage it doesn't matter. If you would like to sort the data, upper-case or lower-case it, or have automatic conversions to different client encodings, you had better tell the server the truth about what it is storing. regards, tom lane