Hi Hackers, (CC people involved in the earlier discussion) Right now, it is possible for the 'inactive_since' value of an invalid replication slot to be updated multiple times, which is unexpected behavior. As suggested in the ongoing thread [1], this patch introduces a new dedicated function to update the inactive_since for a given replication slot, and ensures that inactive_since is not updated for an invalid replication slot.
The v1 patch is attached. Any feedback would be appreciated. [1] https://www.postgresql.org/message-id/CAA4eK1L6A-RC2PkqAFjgmmmS6_vKxrLsG33vdJzeeRKBP8RbOA%40mail.gmail.com -- Thanks, Nisha
v1-0001-Avoid-updating-inactive_since-for-invalid-replica.patch
Description: Binary data
