If it were a file permissions issue, I would suspect it would be an all
or nothing situation, would you not? As I mentioned, the strange thing
is that once you stop and restart the service everything is fine, and it
appears to be triggered by sometimes reloading the config file.
I have gone on and explicitly added the postgresql service account and
given it full access rights to the directory.
Maybe this will keep it from recurring.
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Thursday, May 25, 2006 1:59 PM
To: Benjamin Krajmalnik
Cc: Scott Marlowe; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Strange errors in log file
"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