From: Anibal Acosta <aa@personal.net.py>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Corrupt backup file after pg_dump (from windows)
Date: 12/14/2007 3:16:45 PM
Message-ID: <20071214181644.955107D2794@mail.personal.net.py> (raw)
Hello guys; Days ago I backup my postgres database using the PGAdmin program for windows; my postgres version is 8.1.
Now; when I try to restore the backup an error occur. ( BTW; I format my disk; so I can't backup gain :( )
After restore I check the postgres database and I found all table; functions; and others structures; also data in some tables but not in all.
After some research I detect that I have some "bad blocks" in my backup file. Those blocks are in the DATA section of a large table; maybe in a range of 16K.
So; when I run the pg_restore everything is restored until the damaged sector; all information after it is ignored.
In the console appear "out of memory".
Someones suggest to open the backup file and remove bad rows; but when I open in any text editor the data is not in a human readable way.
So; maybe you know how can I remove all rows stored in damaged bytes in order to restore all others rows after it.
Thanks!!
Anibal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: aa@personal.net.py
Subject: Re: Corrupt backup file after pg_dump (from windows)
In-Reply-To: <20071214181644.955107D2794@mail.personal.net.py>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox