readyprompt opened a new pull request, #6193: URL: https://github.com/apache/couchdb/pull/6193
## Overview The purge infos limit is not explicitly persisted and could be lost if the database closes or the node restarts before it is. The set_purge_infos_limit callback (in couch_bt_engine) updates memory and marks that it needs persisted. The handler for set_purge_infos_limit does not persist the change. All of the other handlers for the header data persist the data. The new limit is not explicitly written to storage. If another write does not occur before the database closes or the node restarts then the header will revert to the last committed value and the configured limit is lost. Commit the set_purge_infos_limit data in the handler instead of depending on another unrelated write. Add cpse_set_purge_infos_limit to the props suite of the storage engine. Modeled after the set_revs_limit test it will set the limit, shut the database down, reopen it and validate the value survived. The current coverage set the limit on an open database and read it back, which just tests whether the change is in memory. ## Checklist - [x] This is my own work, I did not use AI, LLM's or similar technology - [x] Code is written and works correctly - [x] Changes are covered by tests - [ ] Any new configurable parameters are documented in `rel/overlay/etc/default.ini` - [ ] Documentation changes were made in the `src/docs` folder - [ ] Documentation changes were backported (separated PR) to affected branches -- 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]
