Skip to content

now one session will only mapping to one backend process #7

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

Open
digoal opened this issue May 21, 2018 · 1 comment
Open

now one session will only mapping to one backend process #7

digoal opened this issue May 21, 2018 · 1 comment

Comments

@digoal
Copy link

digoal commented May 21, 2018

HI,
now one session will only mapping to one backend process, so when one of the sessoiin attach to the backend process is in idle in transaction mode, so other session's request will waiting which attach to the same process.
can we improve the version, so one session don't need to attach a backend, all backend process can share with all sessions?

@knizhnik
Copy link

Hi
Sorry, I do not completely understand the question.
Backend is able to handle multiple sessions. It is processing statements of one transaction until transaction is finished or client is disconnected. In case of long living transaction, all sessions served by this backend will be blocked. So client should not wait inside transaction (it is also true for normal Postgres, but for built-in connection pool it is much more critical). It is possible to use idle_in_transaction timeout to abort such transactions and prevent blocking of other clients.

I hope I answered your question, if not, please reformulate it.

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

2 participants