Den 2020-01-11 kl. 15:05, skrev Ann Harrison [email protected] [firebird-support]:
> > > On Jan 11, 2020, at 7:37 AM, Kjell Rilbe > [email protected] [firebird-support] > <[email protected]> wrote: > > > > Does gfix -v -full detect all kinds of database corruption? Or are > there > > corruptions that cannot be detected > > Gfix finds only errors in the physical structure of the database. > These include problems like doubly allocated or unallocated pages, bad > back version pointers, and orphaned back version chains. > > Gfix will not find logical data errors like duplicates in a unique > constraint or broken foreign key relationships. > Understood. But I take it then, that gfix -f -full does detect ALL kinds of errors in the physical database structure? A gbak backup + restore cycle should find logical errors, I assume. But a restore with the -inactive switch wouldn't find any violations of constraints that are based on underlying indices, right? I.e. it wouldn't detect duplicates in unique constraints or primary key violations? Regards, Kjell [Non-text portions of this message have been removed]
