fix(relay): drop per-broadcast info logs in broadcast_to_clients - #95
Merged
wolfy-j merged 1 commit intoJul 27, 2026
Merged
Conversation
broadcast_to_clients logged at info on every call and once per connected client. When log streaming is enabled and a client subscribes to the live log topic over this same relay, each broadcast log re-enters the stream and is re-broadcast, self-amplifying into a flood. Remove the two info logs; the fan-out (process.send) is unchanged, and connect/disconnect/error logging stays.
wolfy-j
approved these changes
Jul 27, 2026
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
2 participants
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.
broadcast_to_clients logs at info on every call and once per connected client. When log streaming is enabled (logmanager.stream_to_events) and a client subscribes to the live log topic over this same relay, each broadcast log re-enters the stream and is re-broadcast to that subscriber — which logs again. The result is a self-amplifying flood of "broadcasting topic to clients" whenever a log viewer is open (client_count grows, topic = the log topic).
This removes the two info logs in broadcast_to_clients. The fan-out (process.send) is unchanged; connect/disconnect/plugin/pg/error logging is untouched. Coordinated with the maintainer.