Conversation
This was referenced Sep 3, 2026
…edback Report to PostgreSQL only what the Klio server has actually durably received, instead of the client's own local write/send progress, and deliver that feedback as soon as it's available. The WAL Put RPC becomes bidirectional: the server now streams back a PutResult (write_lsn/flush_lsn) per batch of blocks it flushes, instead of a single result at the very end of the file. Both sides run a background goroutine to shuttle these acks without blocking the hot path, so the client can turn them into standby status updates for PostgreSQL as soon as they arrive, rather than only once the whole file is done. Assisted-by: Claude Co-authored-by: Leonardo Cecchi <leonardo.cecchi@enterprisedb.com> Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.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
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.
Report to PostgreSQL only what the Klio server has actually durably received, instead of the client's own local write/send progress, and deliver that feedback as soon as it's available.
The WAL Put RPC becomes bidirectional: the server now streams back a PutResult (write_lsn/flush_lsn) per batch of blocks it flushes, instead of a single result at the very end of the file. Both sides run a background goroutine to shuttle these acks without blocking the hot path, so the client can turn them into standby status updates for PostgreSQL as soon as they arrive, rather than only once the whole file is done.
Closes #98