On 01/13/2014 01:44 AM, Abraham, Danny wrote:
> Hi,
>
>
>> Are the servers on the Windows versions you mention or the clients or both?
> Both clients as well as server are located on the same Windows Server machine.
>
>> Where is this error showing up, the Windows or Postgres logs?
> Both. It appears in the pg_log as well as failing the client
>
>> What does the other log show?
> Nothing special. Once logged in PG is fine.
>
>> Is there anything preceding the above that might shed light?
> Unfortunately not. Memory problems within Windows (Error 487) used to be common in 8.3.7 ... but got solved in
8.3.15.
> We are now having them again with 9.2.4.
From what I can find WSACancelBlockingCall is a Winsock function has to
do with networking/messaging and not memory issues per se. So what makes
you think it is a memory issue or are the memory problems a separate issue?
See below for more detail on WSACancelBlockingCall, it might help you
determine how to debug:
http://www.sockets.com/winsock.htm#CancelBlockingCall
>
>> Are the connections across a network and if so is there a firewall between the clients and server(s)?
> No FW involved. All the connections are local. This is a pure , inconsistent Server problem.
> See BUG #5578: postrgesql database crash ....
Looked at the bug report and the last comment was from Robert Haas who
indicated there was not enough information to work with. I would say we
are at that same point now.
In your first post you mention that this is related to connection attempts.
So:
What clients are connecting and is it restricted to particular clients?
How many connections are you attempting at a time?
You said many connection refusals are happening, how many as percent of
total?
You also mentioned 'Sometimes it even fails the AUTOVACUM process'.
What does that mean, the AUTOVACUM process cannot connect, it connects
but then fails, other?
Also what is the log entry when AUTOVACUM fails?
>
>
> Thanks
>
> Danny
>
--
Adrian Klaver
adrian.klaver@gmail.com