From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
Cc: | Andrew Sullivan <sullivana(at)bpl(dot)on(dot)ca>, user Postgresql ML <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Hints about how to debug pg_dump problem? |
Date: | 2000-07-25 20:40:45 |
Message-ID: | Pine.LNX.4.21.0007252007450.546-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-07-25 20:40:51 | Re: 4 billion record limit? |
Previous Message | Peter Eisentraut | 2000-07-25 20:40:17 | Re: ROLLBACK automatically |