pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Anibal David Acosta <aa@personal.net.py>
Cc: Phillip Smith <phillip.smith@weatherbeeta.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Please help (backup)
Date: Mon, 22 Oct 2007 09:39:38 -0500
Message-ID: <dcc563d10710220739m133b2c02j858941128abcd85c@mail.gmail.com> (raw)
In-Reply-To: <471C9A26.9090302@personal.net.py>
References: <024701c8147c$55cc9430$9b0014ac@wbaus090>
	<471C9A26.9090302@personal.net.py>

On 10/22/07, Anibal David Acosta <aa@personal.net.py> wrote:
>
>  Really all file content after object definitions looks like
> "Encoded/Encrypted" and when I do a restore all table data are restored
> successfully (except one, that is in the "corrupted sector"). So, maybe the
> pg_dump do a encrypt or something like that over the DATA content.

No. What likely happened is that due to a bug in your OS or harddrive
controller, sectors from the middle of a binary (like an executable)
got put in place of some of your blocks in your postgresql backup.

You need to use a robust editor like vi to chop those parts out and
see what you get.

But the real answer is to use a known good backup.



view thread (5+ messages)

Message-ID: <dcc563d10710220739m133b2c02j858941128abcd85c@mail.gmail.com>
Permalink:  ../dcc563d10710220739m133b2c02j858941128abcd85c@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10710220739m133b2c02j858941128abcd85c@mail.gmail.com

 · 

reply

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: scott.marlowe@gmail.com, aa@personal.net.py, phillip.smith@weatherbeeta.com.au
  Subject: Re: Please help (backup)
  In-Reply-To: <dcc563d10710220739m133b2c02j858941128abcd85c@mail.gmail.com>

* 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