I wonder if we can use something like ^^ to capture the local replay lag. This might be useful if a replica was restarted with replay lag. The replication slot will remain inactive until the local replay has caught up (I think that's right). Adding a local replay lag to the json response could be nice.
I wonder if we can use something like ^^ to capture the local replay lag. This might be useful if a replica was restarted with replay lag. The replication slot will remain inactive until the local replay has caught up (I think that's right). Adding a local replay lag to the json response could be nice.