percona-discussion team mailing list archive

[Vadim Tkachenko <vadim@xxxxxxxxxxx>]

Baron,

1) it does not require modification of on-disk format, we will reuse .ibd header

2) I_S. we should check if we can make it. it should be possible.

3) It seems extremely hard to store it somewhere else, we will need
to come up with our own transactional system over files.


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
> Post to     : percona-discussion@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~percona-discussion
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Vadim Tkachenko, CTO, Percona Inc.
Phone +1-888-401-3403,  Skype: vadimtk153
Schedule meeting: http://tungle.me/VadimTkachenko