PGPool-II issues

PGPool-II issues

Postby urchin » Sun 04 Jul 2010 14:09

I am trying to connect via PGPool and have similar issues as mentioned here:

It would appear doing selects in a transaction causes a problem with my front end application timing out. Yet if I connect via pgadmin from the same machine the query finishes almost instantly < 2s

Via dotconnect the same query can take 10 seconds or not at all and it would appear the transaction is the issue.

Have you any solution to this? or what replication solutions have you tested successfully with dotConnect?
Posts: 5
Joined: Sat 11 Mar 2006 16:12

Postby Shalex » Tue 06 Jul 2010 12:02

As Jp.gouigoux mentioned in that thread (, this problem occured after a restart of pgpool-II or his PostgreSQL Server. In this case the issue is associated with invalid connections that remained in the pool. Connection pool can be cleared with the Devart.Data.PostgreSql.PgSqlConnection.ClearPool() and ClearAllPools() methods, if our provider's pool is used ( Also the reason can be the version (2 or 3) of the protocol you are using in your connection string . We recommend you to use protocol 3. We sometimes encountered such problem with protocol 2 in our autotests. If you use protocol 3, this is rather a network problem.

As for clearing pool of pgpool-II, please refer to the pgpool-II documentation.

2. The performance issue.
Why are you using transaction when performing select? Transaction envolves additional resources, so it can take a bit more time for execution. Besides, how are you using transaction? Here are general tips about transactions: Please post here your code and the call stack when transaction execution hangs.
Devart Team
Posts: 7654
Joined: Thu 14 Aug 2008 12:44

Return to dotConnect for PostgreSQL