bug#14028 -

    ndb crash if trigger record get to big, fix incorrect max size of trigger record
parent 088c7d42
......@@ -2325,7 +2325,7 @@ Backup::execDEFINE_BACKUP_REQ(Signal* signal)
const Uint32 maxInsert[] = {
2048, // Temporarily to solve TR515
//25, // 100 bytes
2048, // 4k
4096, // 4k
16*3000, // Max 16 tuples
};
Uint32 minWrite[] = {
......@@ -3134,7 +3134,7 @@ Backup::execSTART_BACKUP_REQ(Signal* signal)
trigPtr.p->tab_ptr_i = tabPtr.i;
trigPtr.p->logEntry = 0;
trigPtr.p->event = j;
trigPtr.p->maxRecordSize = 2048;
trigPtr.p->maxRecordSize = 4096;
trigPtr.p->operation =
&ptr.p->files.getPtr(ptr.p->logFilePtr)->operation;
trigPtr.p->operation->noOfBytes = 0;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment