Comment 3 for bug 695906

Yasufumi,

What does it practically means if this function is called with sync = true
or false. I think the challenge coming with good name here comes from not
perfect understanding of this option at least by me and Vadim.

On Tue, Jan 18, 2011 at 3:29 AM, Yasufumi Kinoshita <
<email address hidden>> wrote:

> The normal behavior:
> ibuf->size < max_size ----> ibuf_contract(sync) is not called
> ibuf->size > max_size ----> ibuf_contract(sync) is called with sync=TRUE
>
> innodb_ibuf_active_contract = 1 behavior:
> ibuf->size < max_size ----> ibuf_contract(sync) is called with sync=FALSE
> ibuf->size > max_size ----> ibuf_contract(sync) is called with sync=TRUE
>
> it is not based on idleness(of what?)
>
> --
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona Server.
> https://bugs.launchpad.net/bugs/695906
>
> Title:
> Rename XtraDB variables in 5.5
>
> Status in Percona Server with XtraDB:
> Confirmed
>
> Bug description:
> Following https://bugs.launchpad.net/percona-server/+bug/692414
>
> We need to rename XtraDB variableS:
>
> innodb_ibuf_accel_rate
> innodb_ibuf_active_contract
> innodb_ibuf_max_size
>
> We should rename these variables to match the InnoDB name,
> innodb_change_buffering. I suggest:
> innodb_ibuf_accel_rate = innodb_change_buffer_purge_rate
> innodb_ibuf_active_contract = innodb_change_buffer_purge_when =
> <idle,always>
> innodb_ibuf_max_size = innodb_change_buffer_max_size
>
> innodb_pass_corrupt_table
> This should be innodb_corruption_detection = <warn,crash>
>
>
>

--
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Join us for Percona Live Event, San Francisco, Feb 16
http://www.percona.com/events/percona-live-san-francisco-2011/