From: Tom Lane <tgl@sss.pgh.pa.us>
To: Benjamin Krajmalnik <kraj@illumen.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Strange errors in log file
Date: Thu, 25 May 2006 15:59:21 -0400
Message-ID: <15311.1148587161@sss.pgh.pa.us> (raw)
In-Reply-To: <8511B4970E0D124898E973DF496F9B432516E0@stash.stackdump.local>
References: <8511B4970E0D124898E973DF496F9B432516E0@stash.stackdump.local>
"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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, kraj@illumen.com, smarlowe@g2switchworks.com
Subject: Re: Strange errors in log file
In-Reply-To: <15311.1148587161@sss.pgh.pa.us>
References: <8511B4970E0D124898E973DF496F9B432516E0@stash.stackdump.local> <15311.1148587161@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox