Re: DROP DATABASE vs patch to not remove files right away

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: DROP DATABASE vs patch to not remove files right away
Date: 2008-04-16 01:27:47
Message-ID: 19873.1208309267@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2008-04-16 01:40:34 Re: DROP DATABASE vs patch to not remove files right away
Previous Message Tom Lane 2008-04-16 01:21:00 Improving planner variable handling