Re: Win32 hard crash problem

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Win32 hard crash problem
Date: 2006-09-05 22:44:08
Message-ID: 44FDFDB8.6060403@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-09-05 23:00:08 Re: Win32 hard crash problem
Previous Message David Fetter 2006-09-05 22:43:52 Re: Concurrent connections in psql patch