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/04/06 12:16] – [Finding the problem table/index] paul | how_to:repairing_corrupted_database [2020/12/02 08:38] – paul | ||
---|---|---|---|
Line 37: | Line 37: | ||
If ' | If ' | ||
+ | |||
+ | If the problem is in a normal table, then depending on the table name, you may be able to delete the table without losing critical data. Please contact support@pscs.co.uk with the table name and we will be able to tell you what is stored in that table, and how to delete it if that is an appropriate action. | ||
=====unexpected chunk number===== | =====unexpected chunk number===== | ||
Line 50: | Line 52: | ||
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==== | ||
Line 90: | Line 92: | ||
SELECT subject, messagetime, | SELECT subject, messagetime, | ||
and | and | ||
- | SELECT username, folder FROM messages.foldermessages INNER JOIN users.users ON messages.foldermessages.userid=users.users.username | + | SELECT username, folder FROM messages.foldermessages |
this will tell you summary information about the message which may help know which message will been deleted | this will tell you summary information about the message which may help know which message will been deleted |