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 3C0EFD820D for ; Wed, 12 Oct 2005 20:02:34 -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 98933-01 for ; Wed, 12 Oct 2005 23:02:28 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 0CCA7D8201 for ; Wed, 12 Oct 2005 20:02:29 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j9CN2Vd3005057; Wed, 12 Oct 2005 19:02:31 -0400 (EDT) To: Andrew Sullivan Cc: pgsql-admin@postgresql.org Subject: Re: character problem In-reply-to: <20051012212642.GA13571@phlogiston.dyndns.org> References: <4349106C.6080206@infinito.it> <434A2792.1070106@infinito.it> <20560.1128954447@sss.pgh.pa.us> <20051012212642.GA13571@phlogiston.dyndns.org> Comments: In-reply-to Andrew Sullivan message dated "Wed, 12 Oct 2005 17:26:42 -0400" Date: Wed, 12 Oct 2005 19:02:31 -0400 Message-ID: <5056.1129158151@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200510/140 X-Sequence-Number: 19212 Andrew Sullivan writes: > 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). You're right, the documentation basically doesn't explain this at all :-( I'll try to add something. regards, tom lane