X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A31913A49FB for ; Mon, 15 Nov 2004 20:35:56 +0000 (GMT) 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 40949-04 for ; Mon, 15 Nov 2004 20:35:46 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4F3363A49E3 for ; Mon, 15 Nov 2004 20:35:47 +0000 (GMT) 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 iAFKZkfx010479; Mon, 15 Nov 2004 15:35:46 -0500 (EST) To: Christian Fowler Cc: pgsql-admin list Subject: Re: evil characters #bfef cause dump failure In-reply-to: References: <9996.1100547889@sss.pgh.pa.us> Comments: In-reply-to Christian Fowler message dated "Mon, 15 Nov 2004 15:29:38 -0500" Date: Mon, 15 Nov 2004 15:35:46 -0500 Message-ID: <10478.1100550946@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: 200411/120 X-Sequence-Number: 15504 Christian Fowler writes: > [shell]$ env > PGCLIENTENCODING=UNICODE > LANG=en_US.UTF-8 > db=# \encoding > UNICODE I was more concerned about the database encoding, which the above doesn't prove. Try "SHOW server_encoding" regards, tom lane