Re: Effects of dropping a large table - Mailing list pgsql-general

From Rob Sargent
Subject Re: Effects of dropping a large table
Date
Msg-id 7e97caed-e625-867d-a4f9-8512c8db3421@gmail.com
Whole thread Raw
In response to Effects of dropping a large table  (Devin Ivy <devinivy@gmail.com>)
Responses Re: Effects of dropping a large table  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-general
On 7/18/23 11:58, Devin Ivy wrote:
Hi all,
I'm hoping to ensure I understand the implications of dropping a large table and the space being reclaimed by the database and/or OS.  We're using pg v14.

This table is quite large with a primary key and one additional index—all together these are on the order of 1TB.  The primary key and index take-up quite a bit more space than the table itself.  Our hope is to discontinue use of this table and then eventually drop it.  However, the database is under constant load and we'd like to avoid (or at least anticipate) downtime or degraded performance.  The database also replicates to a standby instance.

So in short, what can we expect if we drop this table?  Will the strategy that pg takes to give that space back to the rest of the database and/or OS have significant effects on availability or performance?  Finally, are there any other considerations that we should take into account?  I appreciate your time and input, thanks!

--
Devin Ivy
You might consider deleting portions of the table in separate (consecutive) batches (maybe 5% per delete).  And then truncate table is not logged so that might be an alternative.



pgsql-general by date:

Previous
From: Devin Ivy
Date:
Subject: Effects of dropping a large table
Next
From: Michael Paquier
Date:
Subject: Re: fsync data directory after DB crash