Hi Tina Kevin!
I tried reproducing the issue but I wasn't able to do so. I just dug into this issue in more detail and below are my findings.
(a) In instance_faults table we are soft deleting the records by setting the column to numeric value which can be later archived.
(b) Even if you have thousand of records in the table, the query selects the records based only deleted flag set
(c) instance_faults has column 'detail' which is of mediumtext format which can possibly slown down the query. Since we just put stack trace in detail column so I assume innodb wouldn't use external blob storage page to store it.
Can you please let me know how did you confirm if this method was the reason for the query being too slow ?
Hi Tina Kevin!
I tried reproducing the issue but I wasn't able to do so. I just dug into this issue in more detail and below are my findings.
(a) In instance_faults table we are soft deleting the records by setting the column to numeric value which can be later archived.
(b) Even if you have thousand of records in the table, the query selects the records based only deleted flag set
(c) instance_faults has column 'detail' which is of mediumtext format which can possibly slown down the query. Since we just put stack trace in detail column so I assume innodb wouldn't use external blob storage page to store it.
Can you please let me know how did you confirm if this method was the reason for the query being too slow ?
Thanks,
Siva