Hey everyone, how does the meltanoLabs tap-postgres tap keep track of what's been synced during a logical replication initial full sync? If this initial full sync gets interrupted, how does it know where to pick up from? eg. the transferwise tap looks at xmin and writes it as a bookmark as it goes. If it gets interrupted it'll reference the xmin in the latest bookmark and start up again. I ran into an issue with this implementation and was curious how you handle it. https://github.com/transferwise/pipelinewise-tap-postgres/blob/fa3b75bfb1add98f7c7[…]05e6bcff9ac0b4f779a1/tap_postgres/sync_strategies/full_table.py