Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1sTQl2-00GCUz-LN
	for pgsql-admin@arkaria.postgresql.org; Mon, 15 Jul 2024 18:49:08 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1sTQl1-00CLW7-8h
	for pgsql-admin@arkaria.postgresql.org; Mon, 15 Jul 2024 18:49:07 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <ts@talentstack.to>)
	id 1sTQl0-00CLVw-SX
	for pgsql-admin@lists.postgresql.org; Mon, 15 Jul 2024 18:49:06 +0000
Received: from mail.network-systems-solutions.net ([162.250.175.178])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <ts@talentstack.to>)
	id 1sTQkv-002D1v-CB
	for pgsql-admin@lists.postgresql.org; Mon, 15 Jul 2024 18:49:03 +0000
Received: from messaging.network-systems-solutions.net (unknown
 [192.168.242.37])
	by mail.network-systems-solutions.net (Postfix) with ESMTP id 1DD8F80813
	for <pgsql-admin@lists.postgresql.org>; Mon, 15 Jul 2024 19:26:42 +0000 (UTC)
Received: from aox (localhost [127.0.0.1])
	by messaging.network-systems-solutions.net (Postfix) with ESMTP id
 5ECB08E0736
	for <pgsql-admin@lists.postgresql.org>; Mon, 15 Jul 2024 14:48:53 -0400 (EDT)
Received: from jim@talentstack.to by aox (Archiveopteryx 3.2.0) with
 esmtpsa id 1721069331-3614-3610/6/10; Mon, 15 Jul 2024 18:48:51 +0000
Content-Type: multipart/alternative;
 boundary=------------h1fpR1gRnNSlzVL7XzbBWEqj
Message-Id: <d141b2e2-797c-487a-b492-e4fbeeafad3e@talentstack.to>
Date: Mon, 15 Jul 2024 14:47:28 -0400
Mime-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-CA
To: pgsql-admin@lists.postgresql.org
From: Thomas Simpson <ts@talentstack.to>
Subject: filesystem full during vacuum - space recovery issues
X-NSSLTD-Archiving: Added to store 1 as 91321
X-Scanned-By: MIMEDefang 2.84 on 127.0.1.1
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/d141b2e2-797c-487a-b492-e4fbeeafad3e%40talentstack.to>
Precedence: bulk

--------------h1fpR1gRnNSlzVL7XzbBWEqj
Content-Type: text/plain; charset=utf-8; format=flowed

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


--------------h1fpR1gRnNSlzVL7XzbBWEqj
Content-Type: text/html; charset=utf-8

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi</p>
    <p>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.</p>
    <p>Cleaning down the WAL files got the database restarted (an
      archiving problem led to the initial disk full).</p>
    <p>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.</p>
    <p>My problem now is how do I get this space back to return my free
      space back to where it should be?</p>
    <p>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.</p>
    <p>Any suggestions here?</p>
    <p>Thanks</p>
    <p>Tom</p>
    <p><br>
    </p>
  </body>
</html>

--------------h1fpR1gRnNSlzVL7XzbBWEqj--