| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | denis(dot)patron(at)previnet(dot)it |
| Subject: | BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted |
| Date: | 2020-10-09 13:24:15 |
| Message-ID: | 16663-fe97ccf9932fc800@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
The following bug has been logged on the website:
Bug reference: 16663
Logged by: Denis Patron
Email address: denis(dot)patron(at)previnet(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2020-10-09 16:51:03 | BUG #16664: Problem running django |
| Previous Message | 两个孩子的爹 | 2020-10-09 01:53:17 | Re: BUG #16662: pgbench: error: client 418 script 0 aborted in command 5 query 0: ERROR: invalid page in block 4830 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Banck | 2020-10-09 13:49:56 | Re: Two fsync related performance issues? |
| Previous Message | Fujii Masao | 2020-10-09 13:21:29 | Re: Expansion of our checks for connection-loss errors |