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 F18C83A3B34 for ; Tue, 16 Nov 2004 08:44:24 +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 30408-07 for ; Tue, 16 Nov 2004 08:44:22 +0000 (GMT) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by svr1.postgresql.org (Postfix) with ESMTP id E7D1A3A2B29 for ; Tue, 16 Nov 2004 08:44:22 +0000 (GMT) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id iAG8iBZ20697; Tue, 16 Nov 2004 17:44:11 +0900 Message-ID: <002b01c4cbb8$975c0df0$7201a8c0@mst1x5r347kymb> From: "Iain" To: "Peter Eisentraut" , "Tom Lane" Cc: "pgsql-admin list" References: <007901c4cb7a$1cbddcb0$7201a8c0@mst1x5r347kymb> <12470.1100568891@sss.pgh.pa.us> <200411160818.54201.peter_e@gmx.net> Subject: Re: evil characters #bfef cause dump failure Date: Tue, 16 Nov 2004 17:45:09 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-15"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 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/128 X-Sequence-Number: 15512 Hi, > Recall that in 8.0 the default encoding will be derived from the locale. > So if the postgres account has a reasonable locale set (presumably > chosen somewhere during the system installation), everything will work > out. 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. Thanks for the feedback, Iain