We've noticed that with tap-postgres (transferwise) incremental replication -- using a timestamp key -- we are sometimes missing rows. We noticed that missing row timestamp is slightly before the bookmark. Our best guess is that the missing row is being written in a transaction that starts before the meltano run and finishes after (see image). Is this a known issue with incremental replication? If so are there known workarounds?