xanadu-dev commented on issue #112: URL: https://github.com/apache/cloudberry-backup/issues/112#issuecomment-5286345405
Thanks for the quick response I 100% agree with your suggestion and would prefer to maintain one cluster wide history database and have the ability to filter by database In our use case we would trigger a database clean only after a a successful backup is taken so a `--database` filter would be sufficient and `--db-include` and `--db-exclude` options would not be needed, > The actual issue in the described use case is that `backup-clean` and `history-clean` do not support filtering by database. I think it would be better to keep one cluster history database and add a database filter, for example: > > gpbackman backup-clean \ > --database db1 \ > --older-than-days 7 > > gpbackman history-clean \ > --database db1 \ > --older-than-days 30 > > Alternatively, we could add symmetric `--db-include` and `--db-exclude` options. > > The `database_name` field is already stored in the `backups` table. > > Would database filtering for `backup-clean` and `history-clean` solve your use case? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
