mirror of
https://github.com/pgbackrest/pgbackrest.git
synced 2024-12-14 10:13:05 +02:00
762498f4cd
In the case that no backups were expired but time-based retention was met no archive expiration would occur and the following would be logged: INFO: time-based archive retention not met - archive logs will not be expired In most cases this was harmless, but when retention was first met or if retention was increased, it would require one additional backup to expire earlier WAL. After that expiration worked as normal. Even once expiration was working normally the message would continue to be output, which was pretty misleading since retention had been met, even though there was nothing to do. Bring this code in line with count-based retention, i.e. always log what should be expired at detail level (even if nothing will be expired) and then log info about what was expired (even if nothing is expired). For example: DETAIL: repo1: 11-1 archive retention on backup 20181119-152138F, start = 000000010000000000000002 INFO: repo1: 11-1 no archive to remove |
||
|---|---|---|
| .. | ||
| certificate | ||
| code-count | ||
| data | ||
| lib/pgBackRestTest | ||
| src | ||
| .gitignore | ||
| ci.pl | ||
| container.yaml | ||
| define.yaml | ||
| Dockerfile | ||
| test.pl | ||
| uncrustify.cfg | ||
| Vagrantfile | ||