Enhance HOT update checklist script with additional output details an…#8
Merged
gmartinez-dbai merged 1 commit intomainfrom Dec 16, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request improves the usability and accuracy of the
hot_update_optimization_checklist_json.sqlscript for analyzing PostgreSQL HOT update efficiency. The changes enhance output formatting for automation, add more detailed recommendations, and improve the accuracy of fillfactor reporting.Usability and output improvements:
psqlandjq, clarified recommended flags, and documented optional dependencies for easier downstream automation.QUIET, disabling the pager, and turning off the footer in the script.Data accuracy and reporting enhancements:
base_statsCTE to:fillfactorfrompg_class.reloptions(defaulting to 100 if unset),relidfor size lookups,current_fillfactorto the JSON output for each table, making it easier to correlate recommendations with the present configuration.issuedescription, theactionSQL statement with a context-aware fillfactor value, and thecurrent_fillfactorfor transparency.…d examples