Re: Win32 hard crash problem - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Win32 hard crash problem
Date
Msg-id 877j0geop0.fsf@enterprisedb.com
Whole thread Raw
In response to Re: Win32 hard crash problem  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Win32 hard crash problem  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
"Joshua D. Drake" <jd@commandprompt.com> writes:

> O.k. to recap:
>
> This message will present itself, if connection attempts are made from the Web
> Application (Java/JDBC), or locally via PgAdmin. Once the error message is
> received, all subsequent connection attempts will also result in that same
> message. We do not know if the error occurs before or after authentication.

I think other people have claimed that this message is in libpq and not in
JDBC source code which is inconsistent with this description.

> The only known resolution is to reboot Windows. Using the service control panel
> to shutdown postgresql will fail once the message is received. It is unknown if
> using the task master to individually kill processes will work.

This contradicts your previous email about restarting the postmaster working.

I think you have to sit down and write down *exactly* what sequence of actions
cause what results. Describing them in shorthand like "if connection attempts
are made" is leading to a lot of speculation instead of systematic deductions.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] BUG #2600: dblink compile with SSL missing libraries
Next
From: Tom Lane
Date:
Subject: Re: FE/BE protocol vs. parameterized queries