Re: [GENERAL] table corruption
От | Peter Geoghegan |
---|---|
Тема | Re: [GENERAL] table corruption |
Дата | |
Msg-id | CAH2-Wzn3k1m5HCD=BD2RiFGgWJVMW9J=u43s4ksyvUdcOf+fzw@mail.gmail.com обсуждение исходный текст |
Ответ на | [GENERAL] table corruption (Peter Hunčár <hunci@hunci.sk>) |
Ответы |
Re: [GENERAL] table corruption
|
Список | pgsql-general |
On Mon, Oct 23, 2017 at 7:44 AM, Peter Hunčár <hunci@hunci.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@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: