Comment 10 for bug 721611

Baron,

Yes I read through comments.

I think something like innodb_use_xtrabackup_table_import is good enough

For table I think it should be something like

innodb_corrupt_table_action=assert|block etc

On Sun, Feb 27, 2011 at 1:58 PM, Xaprb <email address hidden> wrote:

> Peter, can you read back through Yasufumi's comments and see what you
> can suggest? He had some well-supported opinions about some of the
> things I suggested -- maybe we can come up with something that
> satisfies all of us. Variable naming is hard.
>
> --
> 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/721611
>
> Title:
> Change XtraDB variables in 5.5
>
> Status in Percona Server with XtraDB:
> Won't Fix
> Status in Percona Server 5.5 series:
> Won't Fix
>
> Bug description:
> After discussion with Baron, we should change names of following
> variables in 5.5:
>
> INNODB_AUTO_LRU_DUMP
> to
> innodb_enable_fast_warmup
>
> INNODB_EXPAND_IMPORT
> to
> innodb_enable_import_tables
>
> INNODB_OVERWRITE_RELAY_LOG_INFO
> to
> innodb_provide_replication_position
>
> INNODB_PASS_CORRUPT_TABLE
> Rename to innodb_stop_on_corrupt_table=0|1 ( default is 1)
>
> And next status variables:
> > INNODB_CHECKPOINT_AGE
> > INNODB_CHECKPOINT_MAX_AGE
> > INNODB_CHECKPOINT_TARGET_AGE
>
> Should be
> INNODB_CHECKPOINT_AGE
> INNODB_CHECKPOINT_AGE_MAX
> INNODB_CHECKPOINT_AGE_TARGET
>

--
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

Looking for MySQL Support ?
http://www.percona.com/support/