percona-discussion team mailing list archive

[Peter Zaitsev <pz@xxxxxxxxxxx>]

Baron,

There are number of features such as compression which only work with Innodb
file per table.
It is also most useful in this case -  you can skip binary copy of some
tables if checksum is the same (for example for backup)

We surely expose it to via information schema.

On Tue, Apr 20, 2010 at 7:03 AM, Baron Schwartz <baron@xxxxxxxxx> wrote:

> Vadim,
>
> The checksum is stored in the .ibd file header and only works if
> innodb_file_per_table is used.  A couple of questions:
>
> 1) does this require a modification to the on-disk file format?
> 2) can we make this appear in the INFORMATION_SCHEMA so it can be
> SELECT-ed?
> 3) can it be stored elsewhere so it doesn't require
> innodb_file_per_table?  Maybe a new data dictionary table?
>
> The main benefit of this functionality from my point of view would be
> to enable something like
> http://code.google.com/p/maatkit/issues/detail?id=91 so we could make
> mk-table-checksum verify replication integrity without any locking.
>
> Baron
>
> On Tue, Apr 20, 2010 at 1:19 AM, Vadim Tkachenko <vadim@xxxxxxxxxxx>
> wrote:
>
> > Live checksums for InnoDB tables
> >
> https://blueprints.launchpad.net/percona-server/+spec/innodb-live-checksum
>
> _______________________________________________
> Mailing list: https://launchpad.net/~percona-discussion<https://launchpad.net/%7Epercona-discussion>
> Post to     : percona-discussion@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~percona-discussion<https://launchpad.net/%7Epercona-discussion>
> More help   : https://help.launchpad.net/ListHelp
>



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

Percona Training Workshops
http://www.percona.com/training/