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 68A7532ADBC for ; Thu, 21 Oct 2004 06:28:37 +0100 (BST) 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 65545-06 for ; Thu, 21 Oct 2004 05:28:26 +0000 (GMT) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by svr1.postgresql.org (Postfix) with ESMTP id ED8E432AE73 for ; Thu, 21 Oct 2004 06:28:14 +0100 (BST) Received: from 51dhy.com (unknown [211.100.22.135]) by svr4.postgresql.org (Postfix) with ESMTP id BE6DC5AF6EA for ; Thu, 21 Oct 2004 03:16:39 +0000 (GMT) Received: from [192.168.1.161] (unknown [221.216.137.190]) by 51dhy.com (CSmail for UNIX) with ESMTP id 2E1FA3CC049 for ; Thu, 21 Oct 2004 11:15:06 +0800 (CST) Message-ID: <4177296A.1000209@qmail.zhengmai.net.cn> Date: Thu, 21 Oct 2004 11:13:46 +0800 From: Weiping User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin list Subject: Re: large dumps won't restore References: <417681FD.7060402@qmail.zhengmai.net.cn> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_RFCI X-Spam-Level: X-Archive-Number: 200410/268 X-Sequence-Number: 15261 Christian Fowler wrote: > > db=# \encoding > UNICODE > > the last four columns in the table are: > > full_name_nd | character varying(200) | > mod_date | timestamp without time zone | > pc_char | character varying(4) | > dim_char | character varying(16) | > > [root@host root]# env |grep LANG > LANG=en_US.UTF-8 > emm. guess you don't have PGCLIENTENCODING setting, what's the contend of full_name_nd? could it contain some multibyte character? try: export PGCLIENTENCODING=UNICODE then reload the dump file, see if the error happens again? I guess there are some problematic character in full_name_nd field. you may use 'less' or 'more' command to check line 169371, see if it contain some weird chars. regards Laser