| From: | Gregory Stark <stark(at)enterprisedb(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-06 20:15:55 |
| Message-ID: | 877j0geop0.fsf@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-06 20:48:55 | Re: FE/BE protocol vs. parameterized queries |
| Previous Message | Tom Lane | 2006-09-06 20:04:58 | Re: BUG #2600: dblink compile with SSL missing libraries |