Number of retained backups sometimes incorrect with various versions #1564
Comments
|
Hi! Thanks for reporting this issues. Can you please do the following?
|
|
Here's the output on an instance which has 18 backups retained (2 more than expected): After that, nothing changed, there are still 18 backups (maybe because of the "dry run"? but why?). |
|
PS: also interesting to note, after 1 week the number of backups on some instances were reduced from 36 (see count output in first message) to now 18. So - somtimes backups ARE being deleted, but not always as it seems. |
By default |
|
Ok, I added the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Database name
PostgreSQL
Issue description
Describe your problem
We observe, that in some cases the number of retained backups is incorrect. In some cases more than the configured number are being retained and sometimes fewer.
Please provide steps to reproduce
Too many:
Too few:
All affected instances run longer than the retention time, for months that is.
There are also instances using the very same versions which are not affected.
Here is a list of all postgres instances on a production cluster with the number of retained backups (all run with wal-g 2.0.0):
We can't find a pattern why it is doing this.
Please add config and wal-g stdout/stderr logs for debug purpose
We didn't see any errors or anomalies in the logs so far.
How can we hunt down the problem?
The text was updated successfully, but these errors were encountered: