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

walsender stuck in wait_for_standby_confirmation. #46

Open
Manju050 opened this issue Aug 9, 2024 · 0 comments
Open

walsender stuck in wait_for_standby_confirmation. #46

Manju050 opened this issue Aug 9, 2024 · 0 comments

Comments

@Manju050
Copy link

Manju050 commented Aug 9, 2024

wal_sender_timeout = 360 secs
1.I am trying to test pg_failover_slots in unique case scenario when standby is down .According to flow of code walsender process will wait in latch defined in wait_for_standby_confirmation() function because standby is lagging.
2.Now I tried to restart subscriber to connect again which resulting in error stating that slot is active for another PID.It seems likes previous walsender process is not able to process the shutdown message ('X') because he is waiting in wait_for_standby_confirmation.Because of this behaviour subscriber needs to wait for wal_sender_timeout to connect again.

Any possibilities of handling subscriber messages while looping in wait_for_standby_confirmation() function?

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

No branches or pull requests

1 participant