Re: Why is INSERT-driven autovacuuming based on pg_class.reltuples?

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>
Subject: Re: Why is INSERT-driven autovacuuming based on pg_class.reltuples?
Date: 2022-01-28 07:22:19
Message-ID: bfbfadf4884160615800df1b3bdb675797bbf997.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2022-01-27 at 12:20 -0800, Peter Geoghegan wrote:
> I can see why the nearby, similar vacthresh and anlthresh variables
> (not shown here) are scaled based on pg_class.reltuples -- that makes
> sense. But why should we follow that example here, with vacinsthresh?

What would you suggest instead? pg_stat_all_tables.n_live_tup?

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2022-01-28 07:26:22 Re: Suppressing useless wakeups in walreceiver
Previous Message Bharath Rupireddy 2022-01-28 06:54:48 Report checkpoint progress with pg_stat_progress_checkpoint (was: Report checkpoint progress in server logs)