{"action":"created","issue":{"url":"https://api.github.com/repos/wal-e/wal-e/issues/366","repository_url":"https://api.github.com/repos/wal-e/wal-e","labels_url":"https://api.github.com/repos/wal-e/wal-e/issues/366/labels{/name}","comments_url":"https://api.github.com/repos/wal-e/wal-e/issues/366/comments","events_url":"https://api.github.com/repos/wal-e/wal-e/issues/366/events","html_url":"https://github.com/wal-e/wal-e/issues/366","id":265342069,"node_id":"MDU6SXNzdWUyNjUzNDIwNjk=","number":366,"title":"Different retention for base backups and WAL segments","user":{"login":"afn","id":2779422,"node_id":"MDQ6VXNlcjI3Nzk0MjI=","avatar_url":"https://avatars1.githubusercontent.com/u/2779422?v=4","gravatar_id":"","url":"https://api.github.com/users/afn","html_url":"https://github.com/afn","followers_url":"https://api.github.com/users/afn/followers","following_url":"https://api.github.com/users/afn/following{/other_user}","gists_url":"https://api.github.com/users/afn/gists{/gist_id}","starred_url":"https://api.github.com/users/afn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/afn/subscriptions","organizations_url":"https://api.github.com/users/afn/orgs","repos_url":"https://api.github.com/users/afn/repos","events_url":"https://api.github.com/users/afn/events{/privacy}","received_events_url":"https://api.github.com/users/afn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2017-10-13T16:10:27Z","updated_at":"2018-07-26T12:17:11Z","closed_at":null,"author_association":"NONE","body":"My understanding (correct me if I'm wrong) is that backups can be recovered using just a base backup, and the WAL segments are only needed to restore to an intermediate state between base backups.\r\n\r\nRunning `wal-e delete retain` or `wal-e delete before` deletes both base backups and WAL segments matching the specified criteria. But it would be useful to be able to have different granularity over different time periods, so that the users who have, say, a scheduled say weekly base backup can do fine-grained recovery (using base backup + WAL segments) for recent history and coarse-grained (using only base backups) for older archives.\r\n\r\nI propose adding a new option to `wal-e delete`, `--wal-only`. Then a retention policy can be enforced by running, say:\r\n\r\n```sh\r\nwal-e delete retain 52             # delete everything after 52 weeks\r\nwal-e delete --wal-only retain 8   # delete WAL files after 8 weeks\r\n```\r\n\r\nThoughts?"},"comment":{"url":"https://api.github.com/repos/wal-e/wal-e/issues/comments/408077767","html_url":"https://github.com/wal-e/wal-e/issues/366#issuecomment-408077767","issue_url":"https://api.github.com/repos/wal-e/wal-e/issues/366","id":408077767,"node_id":"MDEyOklzc3VlQ29tbWVudDQwODA3Nzc2Nw==","user":{"login":"AgDude","id":1122519,"node_id":"MDQ6VXNlcjExMjI1MTk=","avatar_url":"https://avatars1.githubusercontent.com/u/1122519?v=4","gravatar_id":"","url":"https://api.github.com/users/AgDude","html_url":"https://github.com/AgDude","followers_url":"https://api.github.com/users/AgDude/followers","following_url":"https://api.github.com/users/AgDude/following{/other_user}","gists_url":"https://api.github.com/users/AgDude/gists{/gist_id}","starred_url":"https://api.github.com/users/AgDude/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AgDude/subscriptions","organizations_url":"https://api.github.com/users/AgDude/orgs","repos_url":"https://api.github.com/users/AgDude/repos","events_url":"https://api.github.com/users/AgDude/events{/privacy}","received_events_url":"https://api.github.com/users/AgDude/received_events","type":"User","site_admin":false},"created_at":"2018-07-26T12:17:11Z","updated_at":"2018-07-26T12:17:11Z","author_association":"NONE","body":"@ScottKelly Your description above is exactly what I am looking for. Did you implement something to do that in your environment?"}}
{"actor":{"display_login":"AgDude"}}