This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
how_to:repairing_corrupted_database [2016/02/05 11:24] – [Delete the problem message] paul | how_to:repairing_corrupted_database [2018/11/14 10:45] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 20: | Line 20: | ||
Once you have repaired the database you should ideally perform a manual database backup & restore to ensure there are no other problems before restarting VPOP3. | Once you have repaired the database you should ideally perform a manual database backup & restore to ensure there are no other problems before restarting VPOP3. | ||
+ | |||
+ | =====Finding the problem table/ | ||
+ | Often the error message will say something like: | ||
+ | |||
+ | Invalid page header in block x in relation base/ | ||
+ | | ||
+ | These numbers are ' | ||
+ | |||
+ | Go to a command prompt in the VPOP3 directory and run ' | ||
+ | |||
+ | Then type (or copy/paste) | ||
+ | |||
+ | select n.nspname AS schema, c.relname AS tablename, c.relkind as kind from pg_class c inner join pg_namespace n on (c.relnamespace=n.oid) where c.relfilenode=< | ||
+ | | ||
+ | In the above example error message < | ||
+ | |||
+ | If ' | ||
=====unexpected chunk number===== | =====unexpected chunk number===== | ||
Line 33: | Line 50: | ||
Unfortunately, | Unfortunately, | ||
- | Go to a command prompt in the VPOP3 directory and run ' | + | Go to a command prompt in the VPOP3\pgsql\bin |
====Finding the problem message==== | ====Finding the problem message==== |