Hi. I'm using tap-postgres and target-postgres. I'm unable to use log-based replication, so I use a mix of incremental and full_table. I use incremental when I have a good last_modified column and no hard deletes. I use full table when I have a small table with hard deletes. I've set the settings so that I can correctly detect hard deletes. I've now discovered a table that's big and has hard deletes. That doesn't fit into either of my criteria. Now, I'm doing hourly meltano+dbt runs so that my data is fresh for my consumers. Is it possible to do a daily job that runs the problematic table as full table, so that it finds the hard deletes?