(Embedded Sequoia.)
I have a periodic process that creates a backup, compares the number
of backups to a maximum, and deletes any more than the maximum. It
then tries to truncate the recovery log to the point of the oldest
backup we have. This way, I can always install a new server by
restoring the backup and I don't need to keep unneeded statements
around.
To truncate the recovery log, I'm calling deleteLogUpToCheckpoint
(checkpointNameOfOldestBackup). That function calls
deleteLogEntriesBeforeCheckpoint, which figures out the log id
associated with the backup, and deletes statements and checkpoints
between -1 and that. The problem is, if no statements have come in
since my last backup, the checkpoints for my other dumps will get
deleted, since they'd have the same log id.
Am I doing something wrong? Calling the wrong function? I don't see
another good alternative. If this is a sequoia bug, you might change
the behavior of deleteLogEntriesAndCheckpointBetween to not delete
checkpoints that are still referenced by the dump table.
Thanks,
Chris
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
