KamoCRM

Refresh planner statistics after the weekly GeoLite rebuild

PerformanceDaemonService
Ya
10 Agosti 2026, 18:33 UTC
Mwandishi
Kamo
Ahadi ya
638aa0a

YugabyteDB does not auto-analyze, and the staging+rename swap replaces geolite_blocks wholesale -- so after every Sunday sync the planner had no statistics for 5.8M rows. Running ANALYZE here keeps the IP lookup on the range index. With statistics the query measures 1.8ms; without the range index at all it was 8,814ms scanning every row. Failure is caught and logged rather than aborting the sync: stale statistics degrade planning, they do not break correctness.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei