Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not wait for an inactive replication slot to catch up. #36

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ashucoek
Copy link
Contributor

We never know how long it will take for an inactive replication slot to advance. Hence, it doesn't make sense to wait for such slot as it will not allow other active replication slot(s) to synchronize.

We never know how long it will take for an inactive replication
slot to advance. Hence, it doesn't make sense to wait for such
slot as it will *not* allow other active replication slot(s) to
synchronize.
@ashucoek ashucoek closed this Dec 19, 2023
@ashucoek ashucoek reopened this Dec 19, 2023
@ashucoek
Copy link
Contributor Author

This is a new proposal to skip waiting on an inactive replication slot that can block synchronization of the other active running slots.

@rdunklau
Copy link
Contributor

rdunklau commented Jan 9, 2024

@ashucoek have you taken a look at my PR here: #31 ?
This is a completely different approach but it solves the same problem, to avoid blocking running other active slots.
On top of that, for the case when a client only periodically connects to the primary replication slot, the approach I have will be eventually able to catch up and replicate the slot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants