DBTransactionSizeError is only thrown in one situation as far as I can tell, and that is when the commit takes too long (the time to write the change to the database takes too long).

@Ladsgroup any idea what is happening here ? Is the query too complex ? Or were there DB problems last monday ?

Hi, I'm sorry for late response. I was sick.

This is a touch one. If it's happening consistently for this particular image, then it's an issue.
It can be one of many things:

• The deleter removes the row from image table and adds them to filearchive tables, if it has too large blobs such as djvu/pdf metadata, it can be the reason.
• The more likely culprit is that probably the db writes are not happening at the same time. Let me explain a bit. If a write is triggered, mw starts a transaction (and the timer) and wraps everything around this transaction (it's called implicit transaction) and if one fails, everything gets rolled back. My guess is that something writes to the db, then parts of mw tries to do something complicated before doing the rest of the writes expanding the transaction time and making it timeout.

I can figure out what is exactly happening here if you can confirm that this deletion is happening consistently (so I can reproduce the error)