You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our sql queries are (likely) missing a bunch of indices.
The main way this will show up is (eventually) with slow queries once the db is populated. While #609 may help identify these bottlenecks, one can already identify most candidates using explain query plan.
Queries should in general be using indices (search) and avoiding full row scans. Missing indices can therefore be identified, added and rechecked to ensure they're being used.
A more robust solution would involve running this in tests somehow, and ensuring there are no scan involved. There may of course be exceptions, but these can be whitelisted.
The text was updated successfully, but these errors were encountered:
Our sql queries are (likely) missing a bunch of indices.
The main way this will show up is (eventually) with slow queries once the db is populated. While #609 may help identify these bottlenecks, one can already identify most candidates using
explain query plan
.Queries should in general be using indices (
search
) and avoiding full rowscan
s. Missing indices can therefore be identified, added and rechecked to ensure they're being used.A more robust solution would involve running this in tests somehow, and ensuring there are no
scan
involved. There may of course be exceptions, but these can be whitelisted.The text was updated successfully, but these errors were encountered: