public inbox for [email protected]  

help / color / mirror / Atom feed

From: Christoph Moench-Tegeder <[email protected]>
To: pramod gupta <[email protected]>
Cc: [email protected]
Subject: Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?
Date: Mon, 29 Dec 2025 17:09:22 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMxxg=a0PCvrSenxkTSjTsBygh5KJ-bqOo2ZqJvGcsjdiECOWg@mail.gmail.com>
References: <CAMxxg=a0PCvrSenxkTSjTsBygh5KJ-bqOo2ZqJvGcsjdiECOWg@mail.gmail.com>

## pramod gupta ([email protected]):

> How was VACUUM ANALYZE able to reclaim such a large amount of space,
> especially for TOAST data?
> 
> Under what conditions does PostgreSQL reclaim disk space without requiring
> VACUUM FULL or CLUSTER?

https://www.postgresql.org/docs/current/routine-vacuuming.html#VACUUM-FOR-SPACE-RECOVERY
"in the special case where one or more pages at the end of a table
become entirely free and an exclusive table lock can be easily obtained"

Regards,
Christoph

-- 
Spare Space

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox