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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: "denni(dot)pat" <denni(dot)pat(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted
Date: 2020-10-15 23:54:32
Message-ID: CA+hUKGLqDAABdFYTNo82NX+WX-ZtsD3DycEQSo2wPP7VTEMNAQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Thu, Oct 15, 2020 at 8:20 PM denni.pat <denni(dot)pat(at)gmail(dot)com> wrote:
> thanks for the patch.
> Do you think it can be included in the next minor releases or the only
> solution will be to recompile?

I would vote +1 for back-patching a fix for this problem (that is,
pushing it into the minor releases), because I agree that it's very
arguably a bug that we treat the segments differently, and looking
around I do see reports of people having to terminate processes to get
their disk space back. I'd definitely want a consensus on that plan
from some experienced reviewers and testers, though. For anyone
wanting to test this, you might want to set RELSEGSIZE to a smaller
number in src/include/pg_config.h.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-10-16 09:56:25 BUG #16674: The idle connection get created automatically
Previous Message Bruce Momjian 2020-10-15 16:46:38 Re: BUG #16672: Postgres user passwords are corrupted during migration

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-10-16 00:01:01 Re: Some remaining htonl() and ntohl() calls in the code
Previous Message Bruce Momjian 2020-10-15 23:50:19 Re: Wrong example in the bloom documentation