From: | Michael Ma <mikema(at)ficnet(dot)net> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: [ADMIN] Can NOT dump db with 6.4.2's pg_dumpall |
Date: | 2000-02-20 07:49:19 |
Message-ID: | 38AF9C7F.5263EC76@ficnet.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi, Matthew
I have tried to dump tables one by one to identify the table contains
bad value. However I got the following error messages from each dump.
..........
SET TRANSACTION command failed. Explanation from backend: 'ERROR:
parser: parse error at or near "transaction"'.
..........
May I know how you manage to locate the bad value? Or, are there other
ways (may be more complicated) to dump a table/db?
Thanks
Michael
===================
Matthew wrote:
>
> I'm not sure if this will help but I just dealt with a similar problem.
> When I tried to do a pg_dump it would fail. It turned out the culpret
> was one single bad value in one row of one table. Any query that
> returned that value would fail also, so I had to go through an
> interitive process of select statements to identify the offending row.
> Once I found it, I was able to delete the row, and everything worked
> again.
>
> Hope that helps, it was a bear of a problem for me.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Vazsonyi | 2000-02-20 08:21:39 | Re: [ADMIN] the beginners |
Previous Message | Matthew | 2000-02-19 23:49:32 | RE: [ADMIN] Can NOT dump db with 6.4.2's pg_dumpall |