Feature request in v2: Warn if below minimum size

[hyperman2]

autopostgresqlbackup cgecks uf a dump file is empty:

if [ ! -s "${dump_file}" ]; then log_error "Something went wrong '${dump_file}' is empty (no space left on device?)" fi

I would love it if the test checks not for 0 bytes, but for a user-configurable threshold. So i say in the config file

MINIMUM_BACKUP_SIZE=1024

and it warns me if any produced .sql or .pgdump file is less than 1024 bytes.

I ask this because I've managed to get some dumps that are 0 bytes, or only contain a short error message. But after compressing these files, they grow to >0 bytes.

As a bonus, if the total backup size is below some threshold, that would also merit logging an error, but the needed adaptations for this are probably a lot bigger.

[k0lter]

Your 2 requests seems legitimate, I will keep you informed.

[k0lter]

I've added this feature, even if I think that the fix in #14 should avoid to have 0 bytes dumps.

See Changelog for the new option.

[hyperman2]

This works perfectly. Thanks.