Search Postgresql Archives

PostgreSQL dblink's way of manipulation with connections

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have created the named dblink connection, then used db A to call
simultaneously the same procedure twice on db B. I have noticed that
the there is one open connection all the time, and there is second
which appear and disappear continually. Is there a way to use
connection pooling, so that one call could take up one connection and
free it once it has done calculating? Or does dblink use completely
other way of manipulating connections?

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux