-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve slowest queries by adding a new index composited schedue_a for desc sorting #4352
Comments
summary: Top 1 sqls e.g., select ... from ( SELECT disclosure.fec_fitem_sched_a.cmte_id AS cmte_id, ORDER BY anon_1.contb_receipt_dt , anon_1.sub_id ; Analysis/solution -- drop INDEX idx_sched_a_2019_2020_cmte_id_dt_sub_id from CREATE INDEX idx_sched_a_2019_2020_cmte_id_dt_sub_id to CREATE INDEX idx_sched_a_2019_2020_cmte_id_dt_sub_id_desc improve about 2+ times based on the data. |
Jean and I had an discussion to do this on these 2 2019_2020 and 2017_2018 firstly. CREATE INDEX idx_sched_a_2019_2020_cmte_id_dt_sub_id_desc CREATE INDEX idx_sched_a_2017_2018_cmte_id_dt_sub_id_desc drop INDEX disclosure.idx_sched_a_2017_2018_cmte_id_dt_sub_id; |
idx_sched_a_%_cmte_id_dt_sub_id_desc had been created in all fec_fitem_sched_a partition tables in DEV/STG/PRD environment in advance during off-peak hour. The existence of the updated index can be confirmed as described in PR #4386 |
What we're after:
Improve slowest queries by adding a new index composited schedue_a for desc sorting
Completion criteria:
The text was updated successfully, but these errors were encountered: