In the buffered LogMiner commit handler, the commit details are recorded after the last event is dispatched, and if heartbeats are not enabled, the update to the commit details won't happen until the next DML event is observed.

When heartbearts are not enabled, should we track the event index and attempt to set the offset to include the recorded commit in that event? This way we minimize this use case for users. If the last event is somehow filtered, then I'm afraid this is very similar to the same problem with snapshots.

In addition, upon resume when we skip already processed events, the log entry is set to use INFO log level, which can be quite verbose if the transaction in question was a very large transaction. We should likely rethink the logging here to perhaps log the details in another way this reduces the verbosity.