PostgreSQL dblink's way of manipulation with connections

From: Piotr Rekowski <aldislaw(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: PostgreSQL dblink's way of manipulation with connections
Date: 2010-09-06 15:36:56
Message-ID: d11edaa2-5399-41d6-b85c-c2d81a6cce40@k10g2000yqa.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2010-09-06 18:16:47 Re: FC13 RPMs for 9.0 - on postgresql.org ftp, but not in yum repo?
Previous Message Mark Gabriel Paylaga 2010-09-06 14:12:50 Re: Connection pool