Re: Win32 hard crash problem

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:07:41
Message-ID: 20060905230741.GW21195@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:
> 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.

Actually Dave Cramer told me that if the postmaster was stopped and then
restarted, it would start answering fine again. Which would make a lot
of sense.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-09-05 23:09:32 Re: Open items for 8.2
Previous Message Dave Page 2006-09-05 23:03:08 Re: Win32 hard crash problem