As an alternative, we could set recovery_target_inclusive to false in the setup_recovery function. This way, recovery would stop just before the recovery target, allowing the publisher to start replicating exactly from the consistent point. Thoughts?
This sounds to me like a simpler and more correct solution.