-
Notifications
You must be signed in to change notification settings - Fork 2
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: cf/5715~1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: cf/5715
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 5 commits
- 15 files changed
- 2 contributors
Commits on Aug 9, 2025
-
For adding BRIN index support in amcheck we need some tiny changes in BRIN core code: * We need to have tuple descriptor for on-disk storage of BRIN tuples. It is a public field 'bd_disktdesc' in BrinDesc, but to access it we need function 'brtuple_disk_tupdesc' which is internal. This commit makes it extern and renames it to 'brin_tuple_tupdesc'. * For meta page check we need to know pages_per_range upper limit. It's hardcoded now. This commit moves its value to macros BRIN_MAX_PAGES_PER_RANGE so that we can use it in amcheck too.
Configuration menu - View commit details
-
Copy full SHA for fb23da4 - Browse repository at this point
Copy the full SHA fb23da4View commit details -
amcheck: brin_index_check() - index structure check
Adds a new function brin_index_check() for validating BRIN indexes. It incudes next checks: - meta page checks - revmap pointers is valid and points to index tuples with expected range blkno - index tuples have expected format - some special checks for empty_ranges - every index tuple has corresponding revmap item that points to it (optional)
Configuration menu - View commit details
-
Copy full SHA for 1938611 - Browse repository at this point
Copy the full SHA 1938611View commit details -
amcheck: common_verify - register snapshot with indcheckxmin check
Moves check to common_verify. Every index needs it for heapallindexed check.
Configuration menu - View commit details
-
Copy full SHA for db4d177 - Browse repository at this point
Copy the full SHA db4d177View commit details -
amcheck: brin_index_check() - heap all indexed
This commit extends functionality of brin_index_check() with heap_all_indexed check: we validate every index range tuple against every heap tuple within the range using consistentFn. Also, we check here that fields 'has_nulls', 'all_nulls' and 'empty_range' are consistent with the range heap data. It's the most expensive part of the brin_index_check(), so it's optional.
Configuration menu - View commit details
-
Copy full SHA for c3ced0d - Browse repository at this point
Copy the full SHA c3ced0dView commit details -
[CF 5715] v9 - amcheck support for BRIN indexes
This branch was automatically generated by a robot using patches from an email thread registered at: https://commitfest.postgresql.org/patch/5715 The branch will be overwritten each time a new patch version is posted to the thread, and also periodically to check for bitrot caused by changes on the master branch. Patch(es): https://www.postgresql.org/message-id/CAE7r3MLcV=v-Rr8R1_+aeASSmCprnqw+AEvatKGkKXd2QXhjgQ@mail.gmail.com Author(s): Arseniy Mukhin
Commitfest Bot committedAug 9, 2025 Configuration menu - View commit details
-
Copy full SHA for 0f79945 - Browse repository at this point
Copy the full SHA 0f79945View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff cf/5715~1...cf/5715