Re: DROP DATABASE vs patch to not remove files right away - Mailing list pgsql-hackers

From Tom Lane
Subject Re: DROP DATABASE vs patch to not remove files right away
Date
Msg-id 19873.1208309267@sss.pgh.pa.us
Whole thread Raw
In response to Re: DROP DATABASE vs patch to not remove files right away  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: DROP DATABASE vs patch to not remove files right away  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Tom Lane wrote:
>> I think that it should be coded
>> to ignore ENOENT the same as the bgwriter does, and that it should press
>> on and keep trying to delete things even if it gets a failure.

> Perhaps, if it gets ENOENT, record this fact -- and after rmtree
> returns, retry the whole thing.

Er, retry what?  There was, presumably, nothing to delete.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Improving planner variable handling
Next
From: Andrew Dunstan
Date:
Subject: Re: DROP DATABASE vs patch to not remove files right away