Re: BUG #15427: DROP INDEX did not free up disk space

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: ap(at)zip(dot)com(dot)au, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15427: DROP INDEX did not free up disk space
Date: 2018-10-12 04:33:14
Message-ID: 6513.1539318794@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-10-11 23:57:16 -0400, Tom Lane wrote:
>> Uh, what's that got to do with it?

> If you look at the bugreport: As soon as the op, on my suggestion,
> triggered sinval processing (by issuing a SELECT 1;) the space was
> freed. So clearly the open FDs were part of the problem.

TBH, I think the space-freeup was more likely driven off a background
checkpoint completion, which is where the truncation happens.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2018-10-12 04:51:48 Re: BUG #15427: DROP INDEX did not free up disk space
Previous Message Andres Freund 2018-10-12 04:09:58 Re: BUG #15427: DROP INDEX did not free up disk space