Gregory Stark wrote:
> "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.
Yes I am fully aware of that. I am only relaying what the customer said.
>
>> 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.
No, it doesn't. I never said restarting the postmaster would work. I
said rebooting windows, allows postgresql to come back up. Those are
entirely different things.
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
solutionssince 1997 http://www.commandprompt.com/
