From: | tyrrill_ed(at)emc(dot)com |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Problem with pg_dump |
Date: | 2009-01-13 21:38:12 |
Message-ID: | 4FB0C599D8D0B14FA37B46EAD92F2153063CC15A@CORPUSMX60C.corp.emc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Hi All,
I am a developer of a product that uses a postgresql database (currently
version 8.2.3.1). We dump the database using pg_dumpall. We are
finding data corruption in the dump files about twice a month with a few
thousand installations. I have been able to track down the data
corruption to the original dump file created by pg_dumpall. In every
case I've seen of the corruption 1 or 2 characters are missing. The
problem exhibits itself when loading the dump files. Here is an example
where two lines were combined:
ERROR: extra data after last expected column
CONTEXT: COPY ds_targets, line 42: "1180635517879 3001
C:/SQLBackup/1180635517879 3001 C:/System Volume Information/"
The file bad row was:
1180635517879 3001 C:/SQLBackup/1180635517879 3001 C:/System
Volume Information/
It should have been two rows as follows:
1180635517879 3001 C:/SQLBackup/
1180635517879 3001 C:/System Volume Information/
Is this something that is perhaps fixed in postgresql 8.3? Any
assistance in resolving this problem would be appreciated.
Thanks,
Ed
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-01-13 22:04:13 | Re: Strange deadlock error last night |
Previous Message | Tom Lane | 2009-01-13 21:04:17 | Re: Strange deadlock error last night |
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2009-01-13 23:54:20 | Re: Use PSQLFS for photo storage |
Previous Message | Jason Long | 2009-01-13 21:28:18 | Re: Use PSQLFS for photo storage |