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 AB7C53A3C84 for ; Tue, 16 Nov 2004 16:07:00 +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 82941-09 for ; Tue, 16 Nov 2004 16:06:58 +0000 (GMT) Received: from leda.steelsun.com (dsl093-240-204.ral1.dsl.speakeasy.net [66.93.240.204]) by svr1.postgresql.org (Postfix) with ESMTP id 941CF3A3C7F for ; Tue, 16 Nov 2004 16:06:57 +0000 (GMT) Received: from leda.steelsun.com (localhost [127.0.0.1]) by leda.steelsun.com (8.12.11/8.12.8) with ESMTP id iAGG6o85016913 for ; Tue, 16 Nov 2004 11:06:50 -0500 Received: from localhost (cfowler@localhost) by leda.steelsun.com (8.12.11/8.12.11/Submit) with ESMTP id iAGG6o2U016910 for ; Tue, 16 Nov 2004 11:06:50 -0500 X-Authentication-Warning: leda.steelsun.com: cfowler owned process doing -bs Date: Tue, 16 Nov 2004 11:06:50 -0500 (EST) From: Christian Fowler X-X-Sender: cfowler@leda.steelsun.com To: pgsql-admin list Subject: Re: evil characters #bfef cause dump failure In-Reply-To: <1100594222.3393.0.camel@fc3> Message-ID: References: <9996.1100547889@sss.pgh.pa.us> <10478.1100550946@sss.pgh.pa.us> <10656.1100552422@sss.pgh.pa.us> <007901c4cb7a$1cbddcb0$7201a8c0@mst1x5r347kymb> <12470.1100568891@sss.pgh.pa.us> <1100594222.3393.0.camel@fc3> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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/133 X-Sequence-Number: 15517 I strongly agree with this. I have always been uncomfortable selecting "UNICODE" and never quite sure if it is the UTF8, UTF16, or UTF32 encoding. SQL_8BIT or SQL_RAW make much more sense than SQL_ASCII given that Tom said this is a lack of encoding. I fear I might have high-bits chopped off or something. However, back to my problem... if a #bfef character is shoved into a VARCHAR, one's dump is hosed. If I went to various websites and entered this in, I could cause a lot of pain. I believe I noticed some characters (like new line and tab) are converted to <80> or similar. Could/should this be extended to more character ranges - particularly high byte chars for people with the SQL_ASCII (lackof) encoding? On Tue, 16 Nov 2004, Markus Bertheau wrote: > > This is, by the way, a reason why this encoding should be renamed to > SQL_8BIT (or something along these lines) and UNICODE to UTF-8. > > -- > Markus Bertheau > > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend > [ \ / [ >X< Christian Fowler | spider AT viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org