@garybernhardt This seems like it might be vaguely up your alley -- Maybe you can see something I missed?
Show this thread
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 …
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
BRIN indexes are lossy. The index just points to a page which contains at least one matching row, but there's no way the executor can know if all rows match and skip it.
-
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.
- 3 more replies
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.