You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
Does transaction requires a given Postgres connection to be reserved exclusively until commit command or it can be used in another transaction ?
Assuming that someone is using this driver for web application for which all HTTP requests needs transaction, if Postgres connection need to reserved exclusively, then there would be 1 Postgres connection per HTTP request. I wonder How much benefit one might achieve by using this async (non-blocking) driver instead of sync (blocking) jdbc driver ?
The text was updated successfully, but these errors were encountered:
If your full request is running in a transaction, than you need as many connections as you want to serve requests concurrently. You still have the benefits of non-blocking, although your application will only be as responsive as your database backend can be.
Does transaction requires a given Postgres connection to be reserved exclusively until commit command or it can be used in another transaction ?
Assuming that someone is using this driver for web application for which all HTTP requests needs transaction, if Postgres connection need to reserved exclusively, then there would be 1 Postgres connection per HTTP request. I wonder How much benefit one might achieve by using this async (non-blocking) driver instead of sync (blocking) jdbc driver ?
The text was updated successfully, but these errors were encountered: