Re: Long running queries over tcp don’t “respond” to client after completion

[Matthew Lenz]

Here is the performance_schema.events_stages_history_long from that LOAD DATA event. If there are other

*************************** 1. row ***************************
Stage: stage/sql/starting
Duration: 0.0000
*************************** 2. row ***************************
Stage: stage/sql/Executing hook on transaction begin.
Duration: 0.0000
*************************** 3. row ***************************
Stage: stage/sql/starting
Duration: 0.0012
*************************** 4. row ***************************
Stage: stage/sql/checking permissions
Duration: 0.0000
*************************** 5. row ***************************
Stage: stage/sql/Opening tables
Duration: 0.0000
*************************** 6. row ***************************
Stage: stage/sql/System lock
Duration: 0.0000
*************************** 7. row ***************************
Stage: stage/sql/executing
Duration: 685.5673
*************************** 8. row ***************************
Stage: stage/sql/query end
Duration: 0.0000
*************************** 9. row ***************************
Stage: stage/sql/waiting for handler commit
Duration: 0.0035
*************************** 10. row ***************************
Stage: stage/sql/closing tables
Duration: 0.0000
*************************** 11. row ***************************
Stage: stage/sql/freeing items
Duration: 0.0000
*************************** 12. row ***************************
Stage: stage/sql/cleaning up
Duration: 0.0000