A look at the patch that brought a real, vectorised string-rewriting function to the Opteryx execution engine — and why the obvious implementation was the wrong one.
The first version was correct and slow. The second version stopped allocating per row and finally let the matcher breathe.
When the planner has to reason about a view it cannot see through, it has two choices: be conservative, or be clever.
The Parquet page index is fast, but reading it is not free. The break-even point is narrower than most engines admit.
Most data governance is policy theatre. This is the minimum model that still gives security teams something solid to trust.
Showing scan size up-front changes user behaviour more than any quota does. The planner now has to earn its estimate.
Bloom filters are easy to add and hard to keep. The planner should drop them the moment they stop earning their keep.
No posts match that search.
