Repository navigation
Log a lost Postgres listener as a warning, and stamp 5.1.0 - #76
Merged
windischb merged 1 commit intoSep 5, 2026
Merged
Conversation
A lost LISTEN connection is routine -- a proxy idle-timeout, a failover, a network blip -- and the node is resubscribed within a second, with catch-up replaying whatever was missed. Logging it as an error with a stack trace fired every alert on every idle-timeout, while the message itself promised a replay. The warning names the cause; the error, with the exception, is reserved for reconnects that keep failing, which is when someone should look. CHANGELOG stamped for 5.1.0; Modgud runs beta.3 in production without findings beyond this one. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Modgud runs 5.1.0-beta.3 in production and reported one thing: the lost-listener log line is an error with a stack trace although the node is back 0.6 s later and the message itself promises a replay. Anyone with error alerting gets paged on every proxy idle-timeout.
What
ex.Message), no stack trace. The error with the exception is reserved for reconnects that keep failing: third consecutive attempt, which with the 0.5 s / 1 s / 2 s backoff is about 3.5 s in, longer than any idle-timeout or failover.## [5.1.0] - 2026-09-05(website copy synced), with a Changed entry for the log level.Verified
Build, unit suite, Postgres multi-node suite incl. the catch-up tests (which exercise exactly this path).
🤖 Generated with Claude Code