Re: Trigger more frequent autovacuums of heavy insert tables

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
Cc: Melanie Plageman <melanieplageman(at)gmail(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, David Rowley <dgrowley(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Subject: Re: Trigger more frequent autovacuums of heavy insert tables
Date: 2025-03-01 17:50:56
Message-ID: Z8NJAN3JkXqs_AjL@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 01, 2025 at 08:57:52AM +0800, wenhui qiu wrote:
> Based on the comments, the pcnt_unfrozen value could potentially be 0,
> which would indicate that everything is frozen. Therefore, is it necessary
> to handle the case where the value is 0.?

How so? If it's 0, then the insert threshold calculation would produce
autovacuum_vacuum_insert_threshold, just like for an empty table. That
seems like the intended behavior to me.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Doruk Yilmaz 2025-03-01 17:52:23 Re: [Patch] add new parameter to pg_replication_origin_session_setup
Previous Message Alexander Lakhin 2025-03-01 17:00:00 Re: Statistics Import and Export