Re: table corruption

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Peter Hunčár <hunci(at)hunci(dot)sk>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: table corruption
Date: 2017-10-23 15:35:06
Message-ID: CAH2-Wzn3k1m5HCD=BD2RiFGgWJVMW9J=u43s4ksyvUdcOf+fzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Oct 23, 2017 at 7:44 AM, Peter Hunčár <hunci(at)hunci(dot)sk> wrote:
> I know that zero_damaged_pages and vacuum (or restore the table from backup)
> will help, but I want to ask if there is a way to identify affected
> rows/datafiles, so we can 'fix' only the affected data using the
> backup/source data, instead of restoring the whole table?

You might find the latest version of amcheck helpful here:
https://github.com/petergeoghegan/amcheck

It's not really written with repair in mind, since that's such a can
of worms, but it might still help you.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Mead 2017-10-23 15:35:56 Re: Postgres 9.6 fails to start on VMWare
Previous Message Martin Moore 2017-10-23 15:26:06 Re: Postgres 9.6 fails to start on VMWare