Hi Thomas,

>
> Yep! Had several requests already from people complaining their backup
> file is corrupted. One infamous is, with databases having a lot of
> trigger, procedures and interdependencies.
>
> A restore might fail with mismatched parameters (can't recall the exact
> error message) for procedures ... Nasty! The only way out here is to
> have a working database and re-compile all PSQL stuff on parameter list
> changes etc ...
>

The problem isn't exactly a corrupt backup, but a database with undetected
logical errors in the data or metadata. Having the backup check the
validity of the whole database would significantly increase the backup time,
but it is possible. At the moment, for example, gbak doesn't pay any
attention to data constraints like unique and not null. It could recognize
and test them ... at a cost. But the kind of problem you're describing
could be caught by making and restoring a metadata backup - much cheaper
than restoring 100G of data.

Good luck,

Ann


[Non-text portions of this message have been removed]