Re: BUG #15427: DROP INDEX did not free up disk space - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15427: DROP INDEX did not free up disk space
Date
Msg-id 6513.1539318794@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15427: DROP INDEX did not free up disk space  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #15427: DROP INDEX did not free up disk space
List pgsql-bugs
Andres Freund <andres@anarazel.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


pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #15427: DROP INDEX did not free up disk space
Next
From: Andres Freund
Date:
Subject: Re: BUG #15427: DROP INDEX did not free up disk space