> My concern isn't really with the system table, but the RESTORE
> process. If a table gets corrupted or damage and the user/client
> only has a backup of the database, shouldn't there be a way to restore
> and IGNORE this. So I could be able to repair it manually? I've
> tried the -N to ignore validity constraints. But I think that's for
> something else. Mind you, there may be a problem with the system
> table allowing duplicate records.

-N switch is absolutely useless. All it does is that it prevents
creating CHECK constraints on _domains_,
(_field_ level CHECK constraints will be restored anyway)
However, since both kinds of CHECK constraints are always restored
_after_ data are pumped into tables, it is always possible to restore
tables containing invalid (i.e. not passing check contraints) data.

Ivan