| Lists: | pgsql-general |
|---|
| From: | M S <arthur_ringworn(at)yahoo(dot)co(dot)uk> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: failed to unlink, Permission denied |
| Date: | 2007-08-09 12:54:17 |
| Message-ID: | 660585.73718.qm@web25011.mail.ukl.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
> no, but (IMO) 8.2.4 is a required upgrade....so you should be testing
that.
Understood, I'll try an upgrade after my repeat tests have finished.
> The server is unable to delete a file (specifically, a temporary
> table created for sorting). Have you considered any running services
> that may acquire a lock on the table (windows is famous for this).
There is the possibility of other threads inserting into the same table, but wouldn't that be a problem according to my understanding of MVCC. There are no LOCK TABLE statements on this table.
I can't think of any programs which would be locking the files (antivirus or other), but I'll have a look.
> This may also suggest you need to look at the work_mem setting, but
> this is not the issue at hand.
Interesting, I'll pass that on.
> is the error repeatable?
I'm running the tests again with 8.2.3 to get an idea.
Cheers for the help!
___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | M S <arthur_ringworn(at)yahoo(dot)co(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: failed to unlink, Permission denied |
| Date: | 2007-08-09 17:20:09 |
| Message-ID: | 17344.1186680009@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
M S <arthur_ringworn(at)yahoo(dot)co(dot)uk> writes:
> I can't think of any programs which would be locking the files (antivirus o=
> r other), but I'll have a look.
Since it's a temporary file, no other Postgres process would be touching
it. I strongly suspect an antivirus or similar tool is touching the
file just as we try to delete it.
regards, tom lane