X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9D6BED7117 for ; Wed, 12 Oct 2005 18:26:46 -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 41687-01 for ; Wed, 12 Oct 2005 21:26:41 +0000 (GMT) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by svr1.postgresql.org (Postfix) with SMTP id 017C5D7F85 for ; Wed, 12 Oct 2005 18:26:41 -0300 (ADT) Received: (qmail 56414 invoked from network); 12 Oct 2005 21:26:43 -0000 Received: from unknown (HELO phlogiston.dydns.org) (a.sullivan@rogers.com@209.222.54.227 with login) by smtp104.rog.mail.re2.yahoo.com with SMTP; 12 Oct 2005 21:26:43 -0000 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id A0BCB40E6; Wed, 12 Oct 2005 17:26:42 -0400 (EDT) Date: Wed, 12 Oct 2005 17:26:42 -0400 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: character problem Message-ID: <20051012212642.GA13571@phlogiston.dyndns.org> References: <4349106C.6080206@infinito.it> <434A2792.1070106@infinito.it> <20560.1128954447@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20560.1128954447@sss.pgh.pa.us> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.029 required=5 tests=[AWL=-0.021, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200510/139 X-Sequence-Number: 19211 On Mon, Oct 10, 2005 at 10:27:27AM -0400, Tom Lane wrote: > No, SQL_ASCII represents the complete absence of any encoding > knowledge. With this database setting, changing client_encoding is a > complete no-op. Postgres will just absorb and re-emit strings exactly > as they were supplied originally, no matter what client_encoding is. The documents remain pretty confusing about this, assuming I still understand the current state of affairs (always a dangerous assumption). The chart in , for instance, says "SQL_ASCII" supports "ASCII". I'm not sure what to do about this (I've noticed it before, and run into the same quandary). One possibility is to add something like this immediately below the chart in the page above: ---snip--- NOTE: SQL_ASCII _does not_ enforce a 7 bit restriction on insertions. SQL_ASCII does not represent a positive claim that the database knows all the characters to be 7 bit characters. It represents instead the complete absence of any encoding knowledge. Inserting high-bit characters into a database using the SQL_ASCII character set may have unpredictable results. ---snip--- -- Andrew Sullivan | ajs@crankycanuck.ca I remember when computers were frustrating because they *did* exactly what you told them to. That actually seems sort of quaint now. --J.D. Baldwin