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

Generalize socket active n #278

Merged
merged 3 commits into from Dec 28, 2022
Merged

Conversation

seriyps
Copy link
Member

@seriyps seriyps commented Dec 23, 2022

In #275 socket_active option have been implemented for the streaming replication mode. In this PR I expand this option usage to any possible epgsql mode.
It may also partially fix #230

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
* `epgsql` / `epgsqla` / `epgsqli` / copy-mode can be used with `socket_active` option
* `epgsqli` can do fine-grained flow control because it produces `{epgsql, C, socket_passive}` messages
* other interfaces re-activate the socket under the hood as soon as `epgsql_sock` receives
  `tcp_passive` / `ssl_passive`
@seriyps seriyps marked this pull request as ready for review December 23, 2022 19:42
@seriyps seriyps requested a review from davidw December 27, 2022 08:55
@seriyps seriyps merged commit a748d2b into epgsql:devel Dec 28, 2022
@seriyps
Copy link
Member Author

seriyps commented Dec 28, 2022

Thanks @davidw !

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

Successfully merging this pull request may close these issues.

Introduce options in epgsql to deal with potential OOM from statements returning big volumes of data
2 participants