Alvaro Herrera wrote:
Joshua D. Drake wrote:
Alvaro Herrera wrote:
Joshua D. Drake wrote:
Alvaro Herrera wrote:
What I've been wondering all along is whether they are using a
connection pool.
Yes they are using a connection pool. A java based one.
It's quite possible that it's the connection pool that gets confused,
and not PostgreSQL itself. It would be interesting if they change the
connection setting when the "hang" next occurs, to point directly to
PostgreSQL bypassing the connection pool.
Well except when they are connecting with Pgadmin (which wouldn't go
through the connection pool) they get the error as well.
Are you assuming, or did they/you verify that this is indeed the case?
I see no reason to assume that pgAdmin can't connect via a pool.
Verified. They do not connect to the connection pool for pgadmin.
Although I would think pgadmin might have problems connecting to a java
based pool. If I recall, (I could be cranked) JDBC apps can't use pgpool
for example.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
