Added custom index for Log__c.LogRetentionDate__c #553
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The data purge job
LogBatchPurger
filters on the fieldLog__c.LogRetentionDate__c
in several queries to determine which records to delete. In orgs with large data volumes (LDV), the queries can have performance issues because the field is not indexed. Now that custom indexes are generally available (GA), a new custom index for the fieldLog__c.LogRetentionDate__c
should help speed up the LogBatchPurger job (among other things that use this field, such as list views, etc.).