From: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Table space not returned to the OS ? |
Date: | 2022-06-27 09:30:45 |
Message-ID: | 35BEB990-A045-413D-8F0F-EA372754960C@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
A few months back (October) I had upgraded a Postgres instance from v12 —> 14.
The database disk size under /var/lib/postgresql/12 was around 800GB+ back then.
Note, that IIRC I had used hard-linking during the upgrade.
In the database itself, lots of things have changed since.
In fact, that database itself has been dropped at some point and restored from a backup.
As I was running out of disk space, I started investigating and found out that
/var/lib/postgresql/12/main/base/16385 —> 886GB+
/var/lib/postgresql/14 —> 400GB
The last modification date on that directory (../12/) appears to be around a month ago,
When the table with relied 16385 was in fact dropped.
Now, In my update scripts (I use this db as an OLAP) I occasionally run VACUUM.
Is it weird that the 886GB space hasn’t been returned to the OS yet?
What’s the safest way to return it to the OS manually?
Thanks
From | Date | Subject | |
---|---|---|---|
Next Message | Wolfgang Rißler | 2022-06-27 09:31:54 | Re: Differences in Escaped bytea's when creating a plain pg_dump |
Previous Message | David G. Johnston | 2022-06-27 07:32:05 | Re: Differences in Escaped bytea's when creating a plain pg_dump |