MIME-Version: 1.0
From: pramod gupta <mail2sony2010@gmail.com>
Date: Mon, 29 Dec 2025 21:23:26 +0530
Message-ID: <CAMxxg=a0PCvrSenxkTSjTsBygh5KJ-bqOo2ZqJvGcsjdiECOWg@mail.gmail.com>
Subject: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in
 PostgreSQL 16?
To: pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="00000000000012cbd20647193f81"
Archived-At: <https://www.postgresql.org/message-id/CAMxxg%3Da0PCvrSenxkTSjTsBygh5KJ-bqOo2ZqJvGcsjdiECOWg%40mail.gmail.com>
Precedence: bulk

--00000000000012cbd20647193f81
Content-Type: text/plain; charset="UTF-8"

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

Thanks in advance.
Pramod Gupta

--00000000000012cbd20647193f81
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Everyone,<br><br>We have a table with a total size o=
f ~628 GB, out of which ~601 GB was TOAST data.<br>After running VACUUM ANA=
LYZE on a weekly basis, the table size reduced significantly to ~109 GB, in=
dicating a large amount of bloat removal.<br><br>I would like to understand=
:<br><br>How was VACUUM ANALYZE able to reclaim such a large amount of spac=
e, especially for TOAST data?<br><br>Under what conditions does PostgreSQL =
reclaim disk space without requiring VACUUM FULL or CLUSTER?<br><br>Is this=
 behavior expected in PostgreSQL 16, particularly for heavily updated or de=
leted TOASTed columns?<br><br>Any insights or documentation references woul=
d be greatly appreciated.<br><br>PostgreSQL version: 16<br><br>Thanks in ad=
vance.<br>Pramod Gupta</div>

--00000000000012cbd20647193f81--