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 94E593A3D1B for ; Tue, 16 Nov 2004 09:43:58 +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 45212-07 for ; Tue, 16 Nov 2004 09:43:55 +0000 (GMT) Received: from curie.credativ.org (credativ.com [217.160.209.18]) by svr1.postgresql.org (Postfix) with ESMTP id 3C0BB3A3D0B for ; Tue, 16 Nov 2004 09:43:57 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by curie.credativ.org (Postfix) with ESMTP id A510D55B6F; Tue, 16 Nov 2004 10:43:56 +0100 (CET) Received: from www.credativ.de (pD95014D0.dip0.t-ipconnect.de [217.80.20.208]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by curie.credativ.org (Postfix) with ESMTP id 613375598A; Tue, 16 Nov 2004 10:43:55 +0100 (CET) Received: from bell.credativ.de (bell.credativ.de [172.26.14.16]) by www.credativ.de (Postfix) with ESMTP id 0B8531C0029; Tue, 16 Nov 2004 10:43:53 +0100 (CET) From: Peter Eisentraut To: "Iain" Subject: Re: evil characters #bfef cause dump failure Date: Tue, 16 Nov 2004 10:43:52 +0100 User-Agent: KMail/1.6.2 Cc: "Tom Lane" , "pgsql-admin list" References: <200411160818.54201.peter_e@gmx.net> <002b01c4cbb8$975c0df0$7201a8c0@mst1x5r347kymb> In-Reply-To: <002b01c4cbb8$975c0df0$7201a8c0@mst1x5r347kymb> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200411161043.52605.peter_e@gmx.net> X-Virus-Scanned: by AMaViS at credativ.com 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/129 X-Sequence-Number: 15513 Am Dienstag, 16. November 2004 09:45 schrieb Iain: > That's seems pretty reasonable, though I think that standardizing on > unicode (and I guess that means UTF-8) is really the way to go. It was > designed as the universal standard after all. It may have been designed that way, but it is a failure in practice. -- Peter Eisentraut http://developer.postgresql.org/~petere/