From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Options for more aggressive space reclamation in vacuuming?
Date: Sun, 14 May 2023 17:43:07 -0500
Message-ID: <99a9d881-235c-d997-026f-16dbea570c6e@gmail.com> (raw)
In-Reply-To: <CAOC+FBWt3mBTg9rC_M0XThP9Tn9TvdYskucBTqJEDR1d8aNrsQ@mail.gmail.com>
References: <CAOC+FBWt3mBTg9rC_M0XThP9Tn9TvdYskucBTqJEDR1d8aNrsQ@mail.gmail.com>
On 5/14/23 12:45, Wells Oliver wrote:
> Noticed over the last few days how much more space VACUUM FULL reclaims
> (for obvious reasons) and I am wondering if there are any solutions for a
> more fruitful VACUUM without the locks of FULL?
Another tactic for UPDATE-heavy environments is to reduce the table's
fillfactor. As long as an indexed field isn't modified, Postgresql will try
and use in-place updates of these HOT (Heap Only Tuple) records.
--
Born in Arizona, moved to Babylonia.
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: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Options for more aggressive space reclamation in vacuuming?
In-Reply-To: <99a9d881-235c-d997-026f-16dbea570c6e@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 DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox