Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?

From: Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>
To: pramod gupta <mail2sony2010(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?
Date: 2025-12-29 16:09:22
Message-ID: aVKnsqaDXN-RKsBZ@elch.exwg.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

## pramod gupta (mail2sony2010(at)gmail(dot)com):

> 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vincent Veyron 2025-12-29 16:40:23 Re: psql: print values and return the COUNT(*) value to bash?
Previous Message Ron Johnson 2025-12-29 16:06:00 Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?