From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Peter Hunčár <hunci(at)hunci(dot)sk>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: table corruption |
Date: | 2017-10-23 17:19:05 |
Message-ID: | CAOR=d=1gpjqurDfOfD62au0R5zuV6LYzA-8-jnbLMfaTfHmtdw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Oct 23, 2017 at 9:35 AM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> 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
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
Nice to see it included in 10!
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-10-23 17:23:17 | Re: table corruption |
Previous Message | George Neuner | 2017-10-23 16:17:41 | Re: Postgres 9.6 fails to start on VMWare |