Does PG do an index recheck on every row that matches a BRiN index, even for ranges where it should know for certain that all rows match? It seems like it's only skipping the check for rows it's certain are filtered, not rows that match.https://gist.github.com/sgrif/374b53017c2698f35fd4db520f063bf3 …
My understanding is that it contains the max and min values for each range, allowing it to skip ranges which for sure don't match. Same logic should apply to ranges which for sure do match.
-
-
BRIN indexes are (mostly) maintained by auto vacuum in a lazy way so they need to recheck. They don't work anything like traditional indexing.
-
See the link, this was a check where the data is laid out ideally for the index. Manually refreshing the index doesn't affect it
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.