Fix racing conditions in Postgres streamer#1002
Merged
VaguelySerious merged 3 commits intoFeb 23, 2026
Merged
Conversation
🦋 Changeset detectedLatest commit: b4708fb The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
@rovo89 is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
Signed-off-by: Robert Vollmer <rovo89@users.noreply.github.com>
While it might technically work, it hands control back to the Postgres module very early and then relies on microtask scheduling to ensure the correct order. But after parsing the message, the function already uses a mutex for correct ordering of chunks within a stream, so each chunk is queued twice. Parsing synchronously avoids that back-and-forth and makes the code flow easier to follow. Signed-off-by: Robert Vollmer <rovo89@users.noreply.github.com>
rovo89
force-pushed
the
fix/postgres-stream-racing-conditions
branch
from
3ac3271 to
b4708fb
Compare
Contributor
Author
|
Rebased. |
VaguelySerious
approved these changes
Feb 23, 2026
This was referenced Feb 24, 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.
I'm currently building a chat using
DurableAgentand frequently (almost for every message) had missing chunks. Often thetext-startwas missing or some of the words were lost. The chunks are persisted totally fine.Investigations have shown that the chunks were dismissed as out-of-order. Indeed, they arrived at the
listenhandler in a different order than they were processed inwriteToStreamMulti(). Since making the proposed changes - especiallyawaiting the `postgres.notify()´ calls - I haven't seen a single missing chunk.