Timeline for why the postgresql did not using the multi-column index
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 30, 2022 at 22:27 | history | became hot network question | |||
| Oct 30, 2022 at 17:02 | vote | accept | Dolphin | ||
| Oct 30, 2022 at 15:22 | answer | added | jjanes | timeline score: 3 | |
| Oct 30, 2022 at 14:53 | history | edited | Dolphin | CC BY-SA 4.0 |
added 146 characters in body
|
| Oct 30, 2022 at 14:45 | comment | added | Akina | *is it possible to make it using the (sub_source_id,created_time) index? Yes, this is possible. Simply change your data stored in the table and make the prefix of this index highly selective. | |
| Oct 30, 2022 at 14:39 | comment | added | Dolphin |
is it possible to make it using the (sub_source_id,created_time) index? why the postgresql using (sub_source_id, id) index?
|
|
| Oct 30, 2022 at 14:37 | comment | added | Akina |
Why do you think that server should use this index? (sub_source_id, id) - will be used, 99%.
|
|
| Oct 30, 2022 at 14:27 | history | asked | Dolphin | CC BY-SA 4.0 |