Listen/Notify for readStream#428
Merged
Merged
Conversation
kraftp
reviewed
Jun 10, 2026
kraftp
approved these changes
Jun 10, 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.
Replaces the 1-second Thread.sleep polling loop in StreamIterator with PostgreSQL LISTEN/NOTIFY, so stream readers wake immediately when a new value is inserted. The 1-second poll is retained as a fallback timeout and for use when LISTEN/NOTIFY is not available (like CRDB)
A previous PR added Migration 39 which adds the trigger that fires
pg_notify('dbos_streams_channel', workflow_uuid || '::' || key)on every INSERT to the streams table. This PR wires up the reader side.fixes #401