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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 00:50:25
Message-ID: 20080416005025.GJ4429@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-04-16 01:21:00 Improving planner variable handling
Previous Message Bruce Momjian 2008-04-15 23:59:34 Re: pg_terminate_backend() issues