public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?
Date: Mon, 29 Dec 2025 11:06:00 -0500
Message-ID: <CANzqJaBiH+q2qiZiThvLa_LdvGRCY+ydBz0VELQbmmh2No6AJQ@mail.gmail.com> (raw)
In-Reply-To: <CAMxxg=a0PCvrSenxkTSjTsBygh5KJ-bqOo2ZqJvGcsjdiECOWg@mail.gmail.com>
References: <CAMxxg=a0PCvrSenxkTSjTsBygh5KJ-bqOo2ZqJvGcsjdiECOWg@mail.gmail.com>
On Mon, Dec 29, 2025 at 10:53 AM pramod gupta <[email protected]>
wrote:
> Hello Everyone,
>
> We have a table with a total size of ~628 GB, out of which ~601 GB was
> TOAST data.
> After running VACUUM ANALYZE on a weekly basis, the table size reduced
> significantly to ~109 GB, indicating a large amount of bloat removal.
>
> I would like to understand:
>
> 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?
>
> Is this behavior expected in PostgreSQL 16, particularly for heavily
> updated or deleted TOASTed columns?
>
> Any insights or documentation references would be greatly appreciated.
>
> PostgreSQL version: 16
>
See the TRUNCATE option:
https://www.postgresql.org/docs/12/sql-vacuum.html
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
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]
Subject: Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?
In-Reply-To: <CANzqJaBiH+q2qiZiThvLa_LdvGRCY+ydBz0VELQbmmh2No6AJQ@mail.gmail.com>
* 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