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
Affects pelican-backend/workers/extract/dataset_filter.py and pelican-frontend/backend/api/views.py
Older note in 001_base.sql:
-- data_item is the largest and most frequently queried table, so rarely used indexes are avoided. The queries in
-- workers/extract/dataset_filter.py and pelican-frontend/backend/api/views.py are rarely run, so we don't add the
-- indexes for data->>'date', data->'buyer'->>'name' and data->'tender'->'procuringEntity'->>'name' (text_pattern_ops).
The query in views is called for each job in the registry, so it might now make sense to add the index. Per the comment, though, we can check whether it slows down data processing to populate the index.
The text was updated successfully, but these errors were encountered:
Similar to the index added in Kingfisher Process.
Affects
pelican-backend/workers/extract/dataset_filter.py
andpelican-frontend/backend/api/views.py
Older note in 001_base.sql:
The query in
views
is called for each job in the registry, so it might now make sense to add the index. Per the comment, though, we can check whether it slows down data processing to populate the index.The text was updated successfully, but these errors were encountered: