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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted
Date: 2020-12-01 06:01:33
Message-ID: X8XcPZYTHs+0mXK5@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Tue, Dec 01, 2020 at 04:06:48PM +1300, Thomas Munro wrote:
> I felt on balance it was a "bug", since it causes operational
> difficulties for people and was clearly not our intended behaviour,
> and I announced this intention 6 weeks ago.

Oops, sorry for missing this discussion for such a long time :/

> Of course I'll be happy to revert it from the back-branches if
> that's the consensus. Any > other opinions?

If there are no other opinions, I am also fine to rely on your
judgment.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-12-01 07:07:29 BUG #16755: A specification or a bug? Digit drop on CAST from DOUBLE PRECISION to NUMERIC.
Previous Message PG Bug reporting form 2020-12-01 05:43:56 BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2020-12-01 06:08:00 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions
Previous Message Tom Lane 2020-12-01 06:01:20 Re: Improving spin-lock implementation on ARM.