Menu
▾
▴
#83 Simplify semantics for backup generation management
As of now, a backup needs to satisfy keep-data-generations and keep-data-days to be deleted. This is really grab to understand for the user, hence I propose to simplify that and to have backups removed only if they satisfy only one of those conditions. I can barely think of a use case where a user would like to have a backup satisfy both conditions btw...
The same applies for arclog and srvlog for consistency.
Thoughts?
Please correct s/grab/hard/g.
Thanks for proposing.
I really agree with you.
By surveying ticket #74 you created, I found this specification and felt very confusing.
I do not know why the former developer did choose this way.
But I think if we change this behavior, it maybe impose on users modifying the usage of pg_rman.
So I think it is not good to change this in minor version up and is better to do this in next major version up.
How do you think?
Regards,
Yes I definitely agree with that. And now a question: when would be the nest major release timeframe of pg_rman?
Thanks for your agreeing.
The next major release is not scheduled for now, sorry.
But I want to release next minor version with checksum corruption fix in this month and then to try to prepare for next major version up with some fixes and refactoring.
Regards,
Fine for me. I think that we should as well fix #85 before doing any release, I am able to reproduce that on my Linux boxes.