Solve Trigger Maintenance Procedure #1207
Open
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.
Description
The issue being solved in this pull request is a slow-running SQL query that is part of the
run_maintenance
procedure. The query is being executed 41 times, with an average execution time of 335.82 milliseconds and a total execution time of 13.77 seconds.Changes
To optimize the performance of the
run_maintenance
procedure, the following changes have been made:Added a new migration file
20241015185254_optimize_pgpartman_maintenance.sql
that contains SQL statements to optimize the performance of therun_maintenance
procedure. The changes include:Updated the
README.md
file to document the changes made in this pull request and provide guidance on how to apply the database migrations.These changes are expected to significantly improve the performance of the
run_maintenance
procedure and reduce the overall execution time.https://dba.ai/issues/cfc5db58-0b9d-4b6b-8089-a9c5519889f0