Hello,
Thanks for the response. No, I am not a Db2 developer, rather am doing a
research project using MySQL and InnoDB tables. I just have one or two
more questions if you don't mind. Is is possible to capture or keep track
of write-sets in innodb. i.e. After running an update/insert transaction
finding out which rows were affected. This would be much more efficient
for replication and other purposes than making use of the committed SQL
statements from the binary logs. Any help would be appreciated.
Thanks,
Danesh Irani
----------------------------------------------------
Danesh,
are you possibly a DB2 developer :)? DB2 for Unix was written at the IBM
Toronto labs.
Look at /innobase/include/read0read.h, /innobase/include/read0read.ic,
/innobase/include/read0read.c.
Currently there is no limit on the number of MVCC snapshots in InnoDB. The
number is only limited by disk space and the computer memory, because
InnoDB
must keep the history information in its tablespace, and the 'read view'
object for each snapshot in memory as long as the snapshot is being used.
The 'read view' is at trx->read_view, and if it is not NULL, you can use
read_view_print() to print its contents to stderr.
Best regards,
Heikki Tuuri
Innobase Oy
