We need to clearly log that a statement is being interrupted just before the ->Interrupt() method is called - here:

Sometimes, the statement can take a long time to rollback (large DML / DDL (CREATE TABLE AS SELECT) statements for example) - so it appears that the statement ran longer than the query timeout setting for the server/session.

Putting a log entry before interruption will help administrators measure rollback timing more easily, and it will clearly indicate that the query timeout setting is working appropriately.

cc @tsathishkumar