Open Ammutadori075 opened 3 weeks ago
Hello @Ammutadori075,
In fact, your need is already described in the ticket #38.
That being said, my initial plan was to not implement such feature. But I may reconsider that since you asked for.
I have the feeling your request is quit urgent. Unfortunately, I'm not available to work on this improvement for now.
Could you suggest me some workarounds while waiting to implement retention? Currently the database has reached 1.3G and is growing daily.
Is it not just possible to ask for more disk space?
The problem is not disk space, but I wouldn't want the database growing so massively to create problems by slowing down reading and writing on the other databases present.
1 GB is nothing if you worry about performances issues.
Furthermore, you have a misunderstanding on how databases and even disks are behaving.
In short: if the patch place break table is taking more and more spaces, it would only affects readings and writings for the patch place break plugin, nothing else.
Is your feature/enhancement request related to a problem?
The database is growing too fast and we need a function that cleans the information of the placed blocks based on time.
Describe the solution you'd like.
A command or configuration that allows you to choose how long to keep the information
Describe alternatives you've considered.
na
Other
No response