From: Anibal David Acosta <aa@personal.net.py>
To: pgsql-admin@postgresql.org
Subject: Please help (backup)
Date: Sun, 21 Oct 2007 21:16:11 -0400
Message-ID: <471BF9DB.2010301@personal.net.py> (raw)
In-Reply-To: <dcc563d10710210718h4c9dd9efpd81108206105b342@mail.gmail.com>
References: <1192777762.618697.226800@e34g2000pro.googlegroups.com>
<dcc563d10710191105k244a5fecsb59718f9be6a322f@mail.gmail.com>
<1192860050.514202.74290@v23g2000prn.googlegroups.com>
<dcc563d10710210718h4c9dd9efpd81108206105b342@mail.gmail.com>
I have a backup done with "pg_dump" utility.
For some reason the backup file has 8 phisical bad sectors (17 KB of data)
Now when I try to restore the backup all tables are created successfully
and data of almost all tables restores successfully too, but one table
(the most important) appear empty.
When I do a pg_restore <backup_file> its show all sql instructions and
data until arrive to the "damaged sector" and throws a "out of memory"
exception.
I want to know if is possible to fix the backup file removing the blocks
in the "bad sectors" in order to restore all other information.
something like file dump surgery :)
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: Please help (backup)
In-Reply-To: <471BF9DB.2010301@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