Re: Problem with restoring dump (may be tsearch-related)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with restoring dump (may be tsearch-related)
Date: 2002-09-05 16:23:08
Message-ID: 19577.1031242988@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de> writes:
> The entries are quite long, and I don't want to cause too much traffic,
> so I don't dare to give you more than this one example:

> Restore-attempt outputs e.g.:
> psql:alldb1.sql:1434914: ERROR: parser: parse error at or near
> "ckenmuskeln"

Hmm. I see that string in the context

> Wie sich die R&uuml;ckenmuskeln anspannen, wird im Bild aber nicht

What exactly is the string that you've represented here as &uuml; ?
Is that literally what's in the dump file, or has something helpfully
html-ized some weird Unicode sequence?

As far as I can tell, what must be happening is that the COPY data
transfer has been terminated and the regular SQL parser is trying to
make sense of the input starting at "ckenmuskeln anspannen,". I'm
wondering if something is misreading the &uuml; sequence as "\." ...
which would probably be a character-set-encoding kind of problem.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Markus Wollny 2002-09-05 16:45:19 Re: Problem with restoring dump (may be tsearch-related)
Previous Message Tom Lane 2002-09-05 16:08:04 Re: Transaction Id wraparounds