Comment 15 for bug 721611

Is error printed in error log in this case ?

I'm trying to figure out if "warn" is appropritate or do we need something
else ?

On Sun, Mar 6, 2011 at 5:04 PM, Vadim Tkachenko <email address hidden> wrote:

> Peter
>
> Idea is that table is inaccessible and query just returns error.
>
>
> On Sun, Mar 6, 2011 at 4:54 PM, Peter Zaitsev <email address hidden> wrote:
> > Baron, Vadim
> >
> > BTW what exactly happens now when you use "pass_corrupt_table" ? Do we
> > abort given query with error message ?
> > Does table become inaccessible until MySQL restart or does itbecome read
> > only ?
> >
> > On Sun, Mar 6, 2011 at 11:59 AM, Xaprb <email address hidden> wrote:
> >
> >> Here are my final suggestions. After this I can only say "see my many
> >> previous suggestions and my reasons for them" :-)
> >>
> >> Change INNODB_AUTO_LRU_DUMP to innodb_buffer_pool_restore_at_startup
> >> Change INNODB_EXPAND_IMPORT to innodb_import_table_from_xtrabackup
> >> (NOTE this is different from Peter's suggestion, which I think is
> >> confusing)
> >> Change INNODB_OVERWRITE_RELAY_LOG_INFO to
> innodb_recovery_update_relay_log
> >> Change INNODB_PASS_CORRUPT_TABLE to
> innodb_corrupt_table_action=assert|warn
> >> (NOTE: standard InnoDB's behavior is "assert" and this should be the
> >> default)
> >>
> >> --
> >> 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:
> >> Confirmed
> >>
> >> Bug description:
> >> After discussion with Baron, we should change names of following
> >> variables in 5.5:
> >>
> >> INNODB_AUTO_LRU_DUMP
> >> to
> >> innodb_buffer_pool_restore_at_startup
> >>
> >> INNODB_EXPAND_IMPORT
> >> to
> >> innodb_use_xtrabackup_table_import (?)
> >>
> >> INNODB_OVERWRITE_RELAY_LOG_INFO
> >> to
> >> innodb_recovery_update_relay_log
> >>
> >> INNODB_PASS_CORRUPT_TABLE
> >> to
> >> innodb_corrupt_table_action=assert|block (?)
> >>
> >> 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/
> >
> > --
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> > 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:
> > Confirmed
> >
> > Bug description:
> > After discussion with Baron, we should change names of following
> > variables in 5.5:
> >
> > INNODB_AUTO_LRU_DUMP
> > to
> > innodb_buffer_pool_restore_at_startup
> >
> > INNODB_EXPAND_IMPORT
> > to
> > innodb_use_xtrabackup_table_import (?)
> >
> > INNODB_OVERWRITE_RELAY_LOG_INFO
> > to
> > innodb_recovery_update_relay_log
> >
> > INNODB_PASS_CORRUPT_TABLE
> > to
> > innodb_corrupt_table_action=assert|block (?)
> >
> > 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
> >
> > To unsubscribe from this bug, go to:
> > https://bugs.launchpad.net/percona-server/+bug/721611/+subscribe
> >
>
>
>
> --
> Vadim Tkachenko, CTO, Percona Inc.
> Phone +1-888-401-3403, Skype: vadimtk153
> Schedule meeting: http://tungle.me/VadimTkachenko
>

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