autovacuum_freeze_max_age on append-only tables

From: senor <frio_cervesa(at)hotmail(dot)com>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: autovacuum_freeze_max_age on append-only tables
Date: 2022-04-20 23:06:25
Message-ID: DM8PR01MB7016C7C6DCAA853AACEE9039F7F59@DM8PR01MB7016.prod.exchangelabs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi All,
I'm attempting to mimic a new feature in version 13 where INSERTS will trigger vacuum for an append-only table.

I'm using v11 and configuring autovacuum_freeze_max_age to a value representing some number of minutes worth of inserts on a table containing the current day events. I'm looking to understand the details of how the vacuum operates and what to expect and plan for. I first ran into an issue when a script attempted to alter the table to change the value of autovacuum_freeze_max_age while a vacuum was running. I know there is a lock conflict while the vacuum is running but I was under the impression that autovacuum_vacuum_cost_limit would limit the time blocked. The ALTER hung much longer than I expected.

I'm apparently needing an education on how this "to avoid wraparound" vacuum differs from any other. I've seen it referenced as "more aggressive" but I'd like details. An upgrade to 13 is "right around the corner".

Pointers to documentation I might have missed is be appreciated.

-Senor

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2022-04-20 23:18:38 Re: autovacuum_freeze_max_age on append-only tables
Previous Message Siddhartha Gurijala 2022-04-20 22:35:51 Large Data insert on Master server fills up /pgsql base dir when Logical replication (pglogical) is active