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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: DROP DATABASE vs patch to not remove files right away
Date: 2008-04-16 21:41:18
Message-ID: 23717.1208382078@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> Tom Lane wrote:
>> ISTM that we must fix the bgwriter so that ForgetDatabaseFsyncRequests
>> causes PendingUnlinkEntrys for the doomed DB to be thrown away too.

> Because of the asynchronous nature of ForgetDatabaseFsyncRequests, this
> still isn't enough, I'm afraid.

Hm. I notice that there is no bug on Windows because dropdb forces a
checkpoint before it starts to remove files. Maybe the sanest solution
is to just do that on all platforms.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-04-16 21:43:16 Re: Lessons from commit fest
Previous Message Tom Lane 2008-04-16 21:34:57 Re: Lessons from commit fest