Re: Unknown winsock error 10061

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Wojciech Strzałka <wstrzalka(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Unknown winsock error 10061
Date: 2009-07-07 08:50:47
Message-ID: 937d27e10907070150y7a2a318p98aa668b95d06b90@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2009/7/6 Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
> Wojciech Strzałka escribió:
>>
>> 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 detailed 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.  Also 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.  Is
> there a difference?

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

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andreas Pflug 2009-07-07 09:04:50 1-Click 8.4 win32 fails to run scripts
Previous Message Andreas Wenk 2009-07-07 07:33:02 Sugestion a db modele like mysql workbrench