Hi Michael,
I've got it now. The problem was that PgAdminIII doesn't handle well the
escaped characters; and perhaps the long lines makes it unsure.
Trying to restore from the terminal window it works well.
Thank you for your answer, it turned me to the right direction (new lines).
Bye,
-- Csaba Együd
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Michael Fuhr
Sent: Tuesday, October 26, 2004 10:05 PM
To: Egy?d Csaba (Freemail)
Cc: 'Pgsql-General@Postgresql.Org'
Subject: Re: [GENERAL] Error restoring bytea from dump
On Tue, Oct 26, 2004 at 08:51:31PM +0200, Együd Csaba wrote:
>
> the restoration of a dump stops at the line above.
What line above? Are you referring to "Error restoring bytea" in the
subject header? Is that the *exact* error message?
> The dump was created with pgsql 7.3.2 and I need to pump it into a
> 7.4.3 one. Should anybody tell me what the problem can be and how I
> can solve it.
Have extraneous newlines and/or carriage returns made it into the dump?
That might result in "invalid input syntax for type bytea", which isn't the
exact error you mentioned but might be what you meant.
> (There are double apostophes [''] many times in the string - is it
normal???
> Besides of the field separator [','] of course...)
http://www.postgresql.org/docs/7.4/static/sql-syntax.html#SQL-SYNTAX-STRINGS
http://www.postgresql.org/docs/7.4/static/datatype-binary.html
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.778 / Virus Database: 525 - Release Date: 2004.10.15.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.778 / Virus Database: 525 - Release Date: 2004.10.15.
