| Daniel M 2006-01-26, 4:59 pm |
| Hi there,
I experienced the same problem as Alex eight months ago (reference below),
but as there was no answer to his question. So I hope I have more luck:
I got the error "SSL SYSCALL error: A blocking operation was interrupted by
a call to WSACancelBlockingCal
l." which appears to end in a loop, as, when I
discovered it, there have been written already several Gigabytes of
Log-Files with just that entry.
The error occured already two times, unfortunately I just got the log of the
2nd time. It occured right after some autovacuum calls, but I guess they
don't have anything to do with it, as autovacuum runs everyday.
The effect is simply a busy server with having all postgres.exe processes
sharing the 100% of CPU time. The server is a v8.1.1 running on XP Pro.
Part I of this problem you find under
From: "Alex Shepherd" <maillists ( at ) ajsystems ( dot ) co ( dot ) nz>
To: <pgsql-admin ( at ) postgresql ( dot ) org>
Subject: Problem with SSL - Server went 100% Busy
Date: Wed, 11 May 2005 12:41:34 +1200
Thank in advance
Daniel Michulke
____________________
____________________
____________________
_____
Você sabia que com o seu MSN Messenger você faz ligações de PC-papa- PC,
grátis e para qualquer lugar do mundo? É só acessar
http://imagine-msn.com/messenger/de...px?locale=pt-br
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|