| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Benjamin Krajmalnik" <kraj(at)illumen(dot)com> |
| Cc: | "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Strange errors in log file |
| Date: | 2006-05-25 19:59:21 |
| Message-ID: | 15311.1148587161@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"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:
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-25 20:00:43 | Re: pg_clog questions |
| Previous Message | Scott Marlowe | 2006-05-25 19:50:13 | Re: Strange errors in log file |