Interestingly, Intercom are blaming a change of the execution plan on MySQL (RDS Aurora) which raises the question – how can you prepare for such an eventuality?
It seems like the sort of thing that might happen when the statistics are providing the wrong information for carrying out the query (rather than any sort of change to the server/db engine).
Does anyone know how to best protect your service from this?
2 comments
[ 1.2 ms ] story [ 17.2 ms ] threadIt seems like the sort of thing that might happen when the statistics are providing the wrong information for carrying out the query (rather than any sort of change to the server/db engine).
Does anyone know how to best protect your service from this?