"Benjamin Krajmalnik" <kraj@illumen.com> writes:
> Restarting the service resolves the problem, so it is not a file
> permissions issue.
It sure *looks* like a file permissions issue.
FWIW, I see that port/win32/error.c translates these Windows
error codes to EACCES:
ERROR_ACCESS_DENIED
ERROR_CURRENT_DIRECTORY
ERROR_LOCK_VIOLATION
ERROR_SHARING_VIOLATION
ERROR_NETWORK_ACCESS_DENIED
ERROR_CANNOT_MAKE
ERROR_FAIL_I24
ERROR_DRIVE_LOCKED
ERROR_SEEK_ON_DEVICE
ERROR_NOT_LOCKED
ERROR_LOCK_FAILED
It would appear that the underlying problem is one of these.
regards, tom lane