Re: Unknown winsock error 10061 - Mailing list pgsql-bugs

From Dave Page
Subject Re: Unknown winsock error 10061
Date
Msg-id 937d27e10907070150y7a2a318p98aa668b95d06b90@mail.gmail.com
Whole thread Raw
In response to Re: Unknown winsock error 10061  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Unknown winsock error 10061  (Wojciech Strzałka <wstrzalka@gmail.com>)
List pgsql-bugs
2009/7/6 Alvaro Herrera <alvherre@commandprompt.com>:
> Wojciech Strza=C5=82ka escribi=C3=B3:
>>
>> I don't suppose this explains anything but - why not to try (this is
>> DEBUG and has more details, but looks like some information are less det=
ailed than in
>> INFO log level ?? (ie. socket error code is missing):
>
> I suggest you add %p to log_line_prefix to differentiate log lines for
> various processes. =C2=A0Also perhaps you want to set log_error_verbosity=
 to
> VERBOSE to see more details about each message.
>
> Since it has been suggested that the problem may be caused by DLLs
> loaded or not by the processes, I suggest you try to find out which ones
> are attached to each process, when it works and when it doesn't. =C2=A0Is
> there a difference?

Also, try removing the plugin_debugger.dll from
shared_preload_libraries in postgresql.conf to eliminate that from the
equation.


--=20
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: "ajay"
Date:
Subject: BUG #4904: mapping between security ids and account name missing
Next
From: Andreas Pflug
Date:
Subject: 1-Click 8.4 win32 fails to run scripts