Hi Sreekanth,
I doubt auto-recover of the page might be possible, as the header of the page is no more valid & corrupted and not sure whether the corruption occurred in relation of a data or index block.
We have seen some occurrences like this before which got rectified by performing reindexing and vacuum full operations on index or entire table.
If the corrupted relation is a data block & reindexing didn't help, based on your current backup strategy, logical (pg)dump/restore) or PITR may help in recovering from corruption problems provided having in tact valid backups before you faced this error.
Hope this helps you in getting required solution.
Please feel free to reach us if you have any queries.
On Fri, Dec 9, 2016 at 6:16 AM, Sreekanth Palluru <sree4pg@xxxxxxxxx> wrote:
Hi ,I am working on page corruption issue want to know if below scenario is possible1) Insert command from client , I understand heap_insert is called from heampam.c2) Let us say table is full and relation is extended and added a new block3) Tuple is inserted into new page for the block RelationPutHeapTuple/hio.c 4) Later WAL record is inserted through recptr = XLogInsert(RM_HEAP_ID, info);5) Then backend update the PageHeader with WAL LSN details PageSetLSN(page, recptr);If my server got crashed after step 4) is there a possibility that after postgres database restart I get below error when I access the relation or vacuum is run on this relation or taking backup through pg_dump ?ERROR: invalid page header in block 204 of relation base/16413/16900 ?orPostgres can automatically recover the page without throwing any error ?Appreciate your valuable response on this--RegardsSreekanth
