Re: Hints about how to debug pg_dump problem? - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: Hints about how to debug pg_dump problem?
Date
Msg-id Pine.LNX.4.21.0007252007450.546-100000@localhost.localdomain
Whole thread Raw
In response to Re: Hints about how to debug pg_dump problem?  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-general
Philip Warner writes:

> >The read eventually dies with a parse error.  I'm sure there must be
> >something wrong in my source database that I'm getting this, but I don't
> >even know where to begin tracking down the problem.  I've dumped and re-read
> >this database before, but I've added the data that is causing the problem
> >since then.  Obviously, that's what the problem is; I just can't see how the
> >file is getting read.  Any hints as to where to start would be much
> >appreciated.
>
> The simplest thing to do would be to copy the dump file and edit it; break
> it into bits that you can run independantly, and see where the error occurs.
>
> P.S. I assume you are using the pg_dump that came with 7.0.2 or earlier.

If it's 7.0.2 you can run psql with -f (instead of <) and with `-V
ON_ERROR_STOP=on' to get error messages with line numbers and immediate
exit if an error occurs.

--
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden


pgsql-general by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: ROLLBACK automatically
Next
From: Peter Eisentraut
Date:
Subject: Re: 4 billion record limit?