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.
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, May 25, 2006 1:59 PM
To: Benjamin Krajmalnik
Cc: Scott Marlowe; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Strange errors in log file
"Benjamin Krajmalnik" <kraj(at)illumen(dot)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:
It would appear that the underlying problem is one of these.
regards, tom lane
pgsql-admin by date
|Next:||From: Tom Lane||Date: 2006-05-25 20:20:44|
|Subject: Re: pg_clog questions |
|Previous:||From: Averbukh Stella||Date: 2006-05-25 20:10:20|
|Subject: Error linking initdb|