network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 5 months |
| seen | yesterday | |
| stats | profile views | 2 |
|
Feb 7 |
awarded | Notable Question |
|
Aug 16 |
awarded | Popular Question |
|
Jan 14 |
comment |
Fastest way to check if InnoDB table has changed Further story development for those who are interested: forum.percona.com/index.php?t=msg&th=2060&goto=7785&; |
|
Jan 6 |
awarded | Teacher |
|
Jan 3 |
awarded | Scholar |
|
Jan 3 |
accepted | Fastest way to check if InnoDB table has changed |
|
Jan 3 |
answered | Fastest way to check if InnoDB table has changed |
|
Dec 27 |
comment |
Fastest way to check if InnoDB table has changed Didn't know that this is the same site, sorry. |
|
Dec 27 |
comment |
Fastest way to check if InnoDB table has changed Maybe it's OK for a local database, but i have multiple remote slaves, so this is not working... |
|
Dec 22 |
comment |
Fastest way to check if InnoDB table has changed Also selecting from information_schema.tables is kind of slow too... i takes about 300ms to check one table. For comparison doing a "CHECKSUM TABLE" on a MyISAM table with millions of rows with Live Checksum enabled is taking less than a milisecond. |
|
Dec 22 |
comment |
Fastest way to check if InnoDB table has changed Thanks for the answer, but as i said, update_time in information_schema.tables is NULL for InnoDB tables. Also i'm not sure that innodb_max_dirty_pages_pct=0 is a good idea, because it will sacrifice performance... I was thinking about a solution with triggers, to insert a random value at a reference table for each of the watched tables, but then i'll need 3 triggers per table only for this... |
|
Dec 21 |
awarded | Student |
|
Dec 21 |
asked | Fastest way to check if InnoDB table has changed |
