Re: large dumps won't restore

From: Weiping <laser(at)qmail(dot)zhengmai(dot)net(dot)cn>
To: pgsql-admin list <pgsql-admin(at)postgresql(dot)org>
Subject: Re: large dumps won't restore
Date: 2004-10-21 03:13:46
Message-ID: 4177296A.1000209@qmail.zhengmai.net.cn
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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(at)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2004-10-21 03:34:04 Re: REVOKE not working...
Previous Message Chris White (cjwhite) 2004-10-21 01:33:14 Drop table problem