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

From PG Bug reporting form
Subject BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted
Date
Msg-id 16663-fe97ccf9932fc800@postgresql.org
Whole thread Raw
Responses Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      16663
Logged by:          Denis Patron
Email address:      denis.patron@previnet.it
PostgreSQL version: 11.9
Operating system:   CentOS 7
Description:

I have an index, which at the file system level, is made up of multiple
segments (file: <id>.1, <id>.2 ecc). When I DROP INDEX, the index is dropped
in Postgresql but at the file system level, the segments are marked as
"deleted". if I check with the lsof command, I see that the segments are in
use from an idle connection. This does not happen if the index is formed by
only one segment (in my case <1Gb). How can I prevent this?
thanks


pgsql-bugs by date:

Previous
From: "两个孩子的爹"
Date:
Subject: Re: BUG #16662: pgbench: error: client 418 script 0 aborted in command 5 query 0: ERROR: invalid page in block 4830
Next
From: PG Bug reporting form
Date:
Subject: BUG #16664: Problem running django