Alvaro Herrera wrote:
Joshua D. Drake wrote:
Alvaro Herrera wrote:
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Fail in what way. Hang, not connect, or get an error msg?
Just verified with customer. Once the problem occurs the first time, the
customer will continually get the same error message for each subsequent
connection attempt:
server sent data ("D" message) without prior row description ("T"
message)
During the connection attempt? I don't think libpq can report that
message until it tries to do a regular query (might be wrong though).
Is the client using some application that's going to issue a query
immediately on connecting?
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.
Joshua D. Drake
OTOH the connection pool may be the thing with the TickCounter problem.
--
=== 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 5: don't forget to increase your free space map settings
