PostgreSQL dblink's way of manipulation with connections - Mailing list pgsql-general

From Piotr Rekowski
Subject PostgreSQL dblink's way of manipulation with connections
Date
Msg-id d11edaa2-5399-41d6-b85c-c2d81a6cce40@k10g2000yqa.googlegroups.com
Whole thread Raw
List pgsql-general
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?

pgsql-general by date:

Previous
From: Mark Gabriel Paylaga
Date:
Subject: Re: Connection pool
Next
From: "Joshua D. Drake"
Date:
Subject: Re: FC13 RPMs for 9.0 - on postgresql.org ftp, but not in yum repo?