My slow query log is full of entries like the following:
# Query_time: 1.016361 Lock_time: 0.000000 Rows_sent: 0 Rows_examined: 0
SET timestamp=1273826821;
COMMIT;
I guess the set timestamp
command is issued by replication but I don't understand how set timestamp
can take over a second. Any ideas of how to fix this?