Change of recv_n_pool_free_frames default value in InnoDB patches has no effect
Bug #788070 reported by
Alexey Kopytov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Unassigned | ||
1.6 |
Won't Fix
|
Medium
|
Unassigned | ||
2.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.2 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In innodb51.patch and innodb51_
/* Set appropriate value of recv_n_
if (buf_pool_
/* Buffer pool of size greater than 10 MB. */
recv_
}
So if the buffer pool is larger than 10 MB (which is always the case these days) it is "adjusted" to 512, which in case of XtraBackup is actually lower than the re-defined default.
Changed in percona-xtrabackup: | |
status: | New → Confirmed |
tags: | added: cr i16386 |
Changed in percona-xtrabackup: | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
Changed in percona-xtrabackup: | |
importance: | High → Medium |
To post a comment you must log in.
This was actually fixed as a part of the single binary refactoring in 2.2.1-alpha1.