From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: rmtree() failure on Windows |
Date: | 2004-10-25 21:15:23 |
Message-ID: | 28121.1098738923@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> If I increase the sleep time before dropdb enormously (35 secs) the
> unlink errors seem to go away, and instead they become rmdir errors like
> the rest.
Do you have anything equivalent to ps that you could use to check
whether there is still an old backend alive during this interval?
Does Windows forbid deleting a directory that is the current working
directory of some process (assuming they even have the same concept
of cwd as Unixen)? If so, is this the same error symptom you would get?
I am wondering if the rmdir failure occurs because an old backend is
still chdir'd into the database directory.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2004-10-25 21:30:52 | Re: [PATCHES] ARC Memory Usage analysis |
Previous Message | Andrew Dunstan | 2004-10-25 21:01:39 | Re: rmtree() failure on Windows |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2004-10-25 21:30:52 | Re: [PATCHES] ARC Memory Usage analysis |
Previous Message | Andrew Dunstan | 2004-10-25 21:01:39 | Re: rmtree() failure on Windows |