From: | Thomas Simpson <ts(at)talentstack(dot)to> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | filesystem full during vacuum - space recovery issues |
Date: | 2024-07-15 18:47:28 |
Message-ID: | d141b2e2-797c-487a-b492-e4fbeeafad3e@talentstack.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Hi
I have a large database (multi TB) which had a vacuum full running but
the database ran out of space during the rebuild of one of the large
data tables.
Cleaning down the WAL files got the database restarted (an archiving
problem led to the initial disk full).
However, the disk space is still at 99% as it appears the large table
rebuild files are still hanging around using space and have not been
deleted.
My problem now is how do I get this space back to return my free space
back to where it should be?
I tried some scripts to map the data files to relations but this didn't
work as removing some files led to startup failure despite them
appearing to be unrelated to anything in the database - I had to put
them back and then startup worked.
Any suggestions here?
Thanks
Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-07-16 00:58:43 | Re: filesystem full during vacuum - space recovery issues |
Previous Message | khan Affan | 2024-07-15 12:28:02 | Re: RDS Postgres & FreeableMemory issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Tachoires | 2024-07-15 18:50:56 | Re: Compress ReorderBuffer spill files using LZ4 |
Previous Message | Andrey M. Borodin | 2024-07-15 18:47:14 | Re: Sort functions with specialized comparators |