From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, 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 23:00:08 |
Message-ID: | 44FE0178.9010305@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>> On 5-Sep-06, at 6:05 PM, Joshua D. Drake wrote:
>>> Yes they are using a connection pool. A java based one.
>
>> Since java has it's own protocol implementation, this is totally
>> unrelated to any libpq error messages.
>
> Another important point that we've not been given information on:
> when pgAdmin/libpq starts failing like this, exactly what is happening
> with the connection pool? Is it still able to issue queries, and
> if not what happens exactly?
No, when this happens everything stops. The only thing they get back is
that message until they reboot the server. The web app (via
java/connection pool), pgAdmin both give the same error.
Which now that I think about it, seems odd if the message is coming from
libpq yes?
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
=== 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/
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-09-05 23:03:08 | Re: Win32 hard crash problem |
Previous Message | Joshua D. Drake | 2006-09-05 22:44:08 | Re: Win32 hard crash problem |