Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
MariaDB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
MariaDB
Commits
fa2263f4
Commit
fa2263f4
authored
Mar 13, 2006
by
jonas@perch.ndb.mysql.com
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
bug#14028 -
ndb crash if trigger record get to big, fix incorrect max size of trigger record
parent
088c7d42
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
ndb/src/kernel/blocks/backup/Backup.cpp
ndb/src/kernel/blocks/backup/Backup.cpp
+2
-2
No files found.
ndb/src/kernel/blocks/backup/Backup.cpp
View file @
fa2263f4
...
...
@@ -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
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment