We added support for row-change logging to MySQL 5.0. The logged data is similar to row-based replication with changes to the output that make it much easier to parse. Gene Pang
describes this work at 2pm at the conference.
What might be done with this data?
- replicate row changes to a data store that is not MySQL (Teradata, HBase/Hypertable, memcached)
- materialized view maintenance
- change notification
And I
talk at the Percona Performance Conference
at 10:50am today on the InnoDB IO architecture.
3 comments:
Do you plan on documenting this in the google mysql tools pages? It's not in V3, right?
It is in the v3 patch but I need to update the patch next week to pick up a few more bug fixes. The best way to start with it is to look at the my.cnf parameters. It needs more general documentation.
Looking forward to it!
Post a Comment