Fixed an issue where the default fillfactor value for B-tree indexes was incorrect. #9648#9653
Open
pravesh-sharma wants to merge 2 commits intopgadmin-org:masterfrom
Open
Fixed an issue where the default fillfactor value for B-tree indexes was incorrect. #9648#9653pravesh-sharma wants to merge 2 commits intopgadmin-org:masterfrom
pravesh-sharma wants to merge 2 commits intopgadmin-org:masterfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 WalkthroughChange default fillfactor handling: B-tree default reduced from 100 to 90, hash default set to 75, and spgist default set to 90 across index properties templates and corresponding test SQL files. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@web/pgadmin/browser/server_groups/servers/databases/schemas/tables/templates/indexes/sql/11_plus/properties.sql`:
- Around line 47-48: The CASE branch defaults for index fillfactor are wrong:
update the WHEN 'hash' and WHEN 'spgist' branches in the properties.sql CASE
that returns default fillfactor so that 'hash' returns 75 and 'spgist' returns
80 (replace the current 90 values in the WHEN 'hash' and WHEN 'spgist' cases) to
match PostgreSQL's HASH_DEFAULT_FILLFACTOR and SPGIST_DEFAULT_FILLFACTOR.
---
Duplicate comments:
In
`@web/pgadmin/browser/server_groups/servers/databases/schemas/tables/templates/indexes/sql/13_plus/properties.sql`:
- Around line 53-54: The CASE branch defaults for index access methods are
incorrect: change the WHEN 'hash' THEN 90 branch to WHEN 'hash' THEN 75 to match
PostgreSQL's actual default, and verify/correct the WHEN 'spgist' THEN 90 branch
to whatever PostgreSQL's SP-GiST default is (update the WHEN 'spgist' THEN
<correct_value> accordingly); locate these clauses by searching for the WHEN
'hash' and WHEN 'spgist' branches in the properties.sql CASE that maps access
methods to default fillfactor values and update the numeric literals to the
verified defaults.
In
`@web/pgadmin/browser/server_groups/servers/databases/schemas/tables/templates/indexes/sql/15_plus/properties.sql`:
- Around line 54-55: Update the default cost for the 'hash' index type in the
SQL templates so all versions use the correct value: replace the WHEN 'hash'
THEN 90 occurrence in templates 11_plus, 13_plus and 15_plus (the WHEN 'hash'
THEN branches in properties.sql) with the intended default (use 100 to match the
other templates), ensuring the WHEN 'spgist' THEN 90 entry remains unchanged.
.../server_groups/servers/databases/schemas/tables/templates/indexes/sql/11_plus/properties.sql
Outdated
Show resolved
Hide resolved
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.
Summary by CodeRabbit