1
0
mirror of https://github.com/postgrespro/pg_probackup.git synced 2025-03-04 15:51:29 +02:00

[Issue #132] validate is now capable of detecting metadata corruption produced by #132

This commit is contained in:
Grigory Smolkin 2019-10-15 13:00:24 +03:00
parent 251fc8382a
commit f49c1970ef

View File

@ -175,6 +175,28 @@ pgBackupValidate(pgBackup *backup, pgRestoreParams *params)
elog(WARNING, "Backup %s data files are corrupted", base36enc(backup->start_time));
else
elog(INFO, "Backup %s data files are valid", base36enc(backup->start_time));
/* Issue #132 kludge */
if (!corrupted &&
((parse_program_version(backup->program_version) == 20104)||
(parse_program_version(backup->program_version) == 20105)||
(parse_program_version(backup->program_version) == 20201)))
{
char path[MAXPGPATH];
pgBackupGetPath(backup, path, lengthof(path), DATABASE_FILE_LIST);
if (pgFileSize(path) >= (BLCKSZ*500))
{
elog(WARNING, "Backup %s is a victim of metadata corruption. "
"Additional information can be found here: "
"https://github.com/postgrespro/pg_probackup/issues/132",
base36enc(backup->start_time));
backup->status = BACKUP_STATUS_CORRUPT;
write_backup_status(backup, BACKUP_STATUS_CORRUPT, instance_name);
}
}
}
/*