Comments on: Global Transaction ID and other patches available!

By: Kevin Burton

Kevin Burton — Sat, 16 May 2009 06:48:15 +0000

We use this primarily to do slave clones….. I saw your note about xtrabackup doing clones but I have not yet had a chance to look at it.

Our current setup works

By: Vadim

Vadim — Sat, 16 May 2009 06:46:26 +0000

Kevin,

How do you do backups ? Why do you need innodb freeze ? As I said we think xtrabackup makes innodb freeze unneeded.
But if you still interested in innodb_freeze you know how to contact us

By: Kevin Burton

Kevin Burton — Sat, 16 May 2009 06:34:15 +0000

We’ve been using innodb freeze for a while now but I think that in conjunction with LVM snapshots we’ve been avoiding any bugs with it…

It’s redundant now though with LVM snapshots.

We were using innodb freeze BEFORE we started using LVM to bypass a bug in xfs_freeze…

Would be nice if it were fixed though so that we don’t have to rely on LVM.

By: Mark Callaghan

Mark Callaghan — Thu, 14 May 2009 18:10:03 +0000

The innodb-freeze patch needs much more work to be stable in production.

The global transaction id patch is published for 5.0. Row-based replication is not available in 5.0.

By: Vadim

Vadim — Thu, 14 May 2009 17:34:47 +0000

uxio,

As far as I understand global_transaction_id does not work with row-level replication.

By: Vadim

Vadim — Thu, 14 May 2009 17:34:03 +0000

uxio,

No we are not going to add innodb-freeze to xtradb, we have xtrabackup to cover our backup needs.

By: uxio

uxio — Thu, 14 May 2009 10:46:35 +0000

global-transaction-id will support row based replication?

By: uxio

uxio — Thu, 14 May 2009 10:44:44 +0000

will you add the innodb-freeze patch to xtradb?

By: Mark Callaghan

Mark Callaghan — Thu, 14 May 2009 00:10:10 +0000

Justin did a great job on this and I can’t wait for it to show up in a Percona binary.