Dinesh Bhandary wrote: > Hello Everybody - > > Due to hardware crash we ran into issues where some blocks were > corrupted and some files were missing. > I was able to get over the corrupted blocks ( errmsg - "invalid page > header in block 12345 of realtion x") by setting > zero_damaged_pages=0 and running vacuum afterwards. Now I am running > into situations where pg_clog files are missing (errmsg - "could not > open pg_clog/0D0D). I have a backup which is quite old ( considering > this as a last resort). Is there any other way to fix this problem? If those clog numbers are not in your usual range, it usually means the row is corrupt and is referring to an corrupt xid number, so the row is bad, not the clog files are missing. > > I also created empty blocks to fool postgres, but there are so many of > these file missing I was wondering if there a better/faster way to fix > this problem. Seems you will have to clear those pages too somehow. I have seen it done with dd. -- Bruce Momjian <bruce@xxxxxxxxxx> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
