Logging | Errors should include reference query transaction ID

debug.log / message currently log errors in query execution but dont reference what query caused or errored, making traceability really hard to impossible when concurrent actions happen

Example:

Apr  8 08:57:25 mcs1prod ddlpackageproc[529551]: 25.882922 |0|0|0| E 23 CAL0009: Error in dropping table from systables. MCS-2045: At least one PrimProc closed the connection unexpectedly.

Apr  8 08:59:26 mcs1prod dmlpackageproc[529518]: 26.766687 |0|0|0| E 21 CAL0001: dmlprocessor.cpp PackageHandler::run() package type 2 MCS-2045: At least one PrimProc closed the connection unexpectedly.

What table had issues dropping from systables?
What query was interupted by PrimProc closed the connection ?

In debug.log, sql statements have internal transaction IDS, we need to reference those during the error output, or even making it human readable where possible