Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read your own writes #2

Open
zknill opened this issue Aug 9, 2023 · 0 comments
Open

Read your own writes #2

zknill opened this issue Aug 9, 2023 · 0 comments

Comments

@zknill
Copy link
Owner

zknill commented Aug 9, 2023

Currently the writes are forwarded to the upstream postgres server, the write request as processed by SQLedge can return before the data is received back to SQLedge on the replication connection. This breaks the read-your-own-writes property.

Implement a feature/config that allows proxied writes to wait for the written data to be received back from the replication protocol before returning.

This could probably be off by default, as it will introduce more latency than the write alone (as we wait to received the write back).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant