pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Weiping <laser@qmail.zhengmai.net.cn>
To: pgsql-admin list <pgsql-admin@postgresql.org>
Subject: Re: large dumps won't restore
Date: Thu, 21 Oct 2004 11:13:46 +0800
Message-ID: <4177296A.1000209@qmail.zhengmai.net.cn> (raw)
In-Reply-To: <Pine.LNX.4.61.0410201140250.26812@leda.steelsun.com>
References: <Pine.LNX.4.61.0410181113470.12648@leda.steelsun.com>
	<417681FD.7060402@qmail.zhengmai.net.cn>
	<Pine.LNX.4.61.0410201140250.26812@leda.steelsun.com>

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




view thread (5+ messages)

Message-ID: <4177296A.1000209@qmail.zhengmai.net.cn>
Permalink:  ../4177296A.1000209@qmail.zhengmai.net.cn/
Also on:    postgresql.org/message-id/4177296A.1000209@qmail.zhengmai.net.cn

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: laser@qmail.zhengmai.net.cn
  Subject: Re: large dumps won't restore
  In-Reply-To: <4177296A.1000209@qmail.zhengmai.net.cn>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox