Hi all, We were bitten by this same bug over the weekend (PG 8.1.3 / Windows Server 2003). The exact error was:
FATAL: semctl(170688872, 6, SETVAL, 0) failed: A non-blocking socket operation could not be completed immediately. The start of the errors corresponded to a nightly "vacuum analyze" (both Saturday and Sunday) run. Things appeared to clear up after the "vacuum analyze" completed. One thing of note is that the semctl parameters were identical across both nights (and a smaller incident Monday morning). The Monday morning occurence was also somewhat odd in that not much should have been going on then. Also, three other servers which faced identical update/insert transaction streams did not have any trouble. The select load might have been higher on the server that failed though. One question I had: In src/backend/port/win32/sema.c, semctl() is implemented in terms of a call to semop(). However, the man page for semctl() doesn't list EAGAIN and EINTR as possible error returns, whereas for semop() it does. Is that just a mistake in the man page or a problem with the Win32 emulation call? (See also http://archives.postgresql.org/pgsql-bugs/2006-02/msg00233.php ) I'm afraid we're in the same category as everyone else with no good way to reproduce the bug, but is there anything else we could do if this happens again? Pete ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings