Re: Trigger more frequent autovacuums of heavy insert tables

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Nathan Bossart <nathandbossart(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-02-25 16:36:04
Message-ID: CAKAnmmLhP3TkNkZbX+BJ-tj8x59pTjk42Vf=MLrX9DtEP4u1Lw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 25, 2025 at 11:03 AM Melanie Plageman <melanieplageman(at)gmail(dot)com>
wrote:

> Because users can now manually update these values in pg_class, there
> wouldn't be a way to detect the difference
> between a bogus relallfrozen value due to VM corruption or a bogus value
> due to manual statistics intervention.

Er..you had me until this. If manual monkeying of the system catalogs leads
to a "bogus" error that resembles a real one, then sow the wind, and reap
the whirlwind. I don't think that should be a consideration here.

--
Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shubham Khanna 2025-02-25 16:49:06 Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.
Previous Message Nathan Bossart 2025-02-25 16:31:56 Re: Trigger more frequent autovacuums of heavy insert tables