Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted - Mailing list pgsql-bugs

From Pavel Borisov
Subject Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted
Date
Msg-id CALT9ZEGD_QdW2n2_R5vhuxAES5OtvEdiZcp9QQBrPk298mwntA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-bugs
Thomas, 
I get into the patch and I think it's worth being committed and backpatched. 
BTW I noticed that sometimes the same comparisons are done twice, and I made a very minor refactor of the code. PFA v2 of a patch if you don't mind.
As for the question on what to do with the additional segments if the first one failed to be truncated, I don't consider myself experienced enough and surely someone else's independent opinion is very much welcome. 

--
Best regards,
Pavel Borisov

Postgres Professional: http://postgrespro.com
Attachment

pgsql-bugs by date:

Previous
From: Kurt Roeckx
Date:
Subject: Re: BUG #16707: Memory leak
Next
From: Peter Eisentraut
Date:
Subject: Re: pg should ignore u+200b zero width space