Comment 2 for bug 600795

I have a fix for this. It was made slightly more complicated by the fact that a LOAD DATA statement has the potential to create a large Transaction object (as large as the data being loaded).

To correct this, we will be introducing a new variable to set a transaction message size threshold. When this a Transaction message size exceeds this threshold, we will finalize the Transaction message and create a new one with the same transaction id. The end_segment variable for the Statements within the Transaction will be set to FALSE to indicate more data is to come.

Waiting for some changes to the system variables framework before I can commit my changes.