> I wonder if it would be better to include a check for the return value of > `durable_rename` to > manage potential failure scenarios.
Or we can be smarter and make this call an ERROR.
One issue with this approach is that if a failure occurs during rename, we cannot unlink(INJ_DUMP_FILE_TMP), because durable_rename does not handle this before throwing an error.
Should we also consider unlinking the target file INJ_DUMP_FILE in case of an error during renaming? Since target files are already synced at the start in the durable_rename() function.
