21.05.2018 14:58, Rashid Abzalov wrote:
21.05.2018 14:42, Vlad Khorsun via Firebird-devel wrote:
I don't see how persistent connections in Postgres could be reused by
different user sessions.
No, in Postgres you can reuse only your own connections.
You see - all approaches have its weak and strong points :)
Nevertheless, it seems to me that this approach also solves the original task
that faced the implementation of the connection pool.
Not agree. Connection pool allows to minimize number of simultaneously
open external connections. Also it allows to avoid cost of connect\disconnect
in case of many short-lived user connections actively works with external
data sources. And this was the main goal as users complains on performance.
But you do not need to deal with the side effects of managing this pool by the
system, not the user.
Because reset the state of the session is half the task, and often this will not solve the problem, because sometimes you need to
execute queries in the context of the previous state. That is, on a good need to implement a reset state somewhere out, and then
restore it from there (on request or maybe always).
It makes sence. But currently we have no way to reuse external connection
and there is no existing applications that depends on external connection
state.
Probably we should take into account this PG feature when (if) implement
persistent external data sources.
Regards,
Vlad
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
