Re: n_ins_since_vacuum stats for aborted transactions - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: n_ins_since_vacuum stats for aborted transactions
Date
Msg-id CAKFQuwb02TUjJXBRqkm8d=wA8uysttAPfTkUfDzr6uLUSVifZg@mail.gmail.com
Whole thread Raw
In response to Re: n_ins_since_vacuum stats for aborted transactions  (Sami Imseih <samimseih@gmail.com>)
List pgsql-hackers
On Wednesday, April 9, 2025, Sami Imseih <samimseih@gmail.com> wrote:

In other words, the reason n_ins_since_vacuum was introduced is to freeze
(committed) rows, so it should not need to track dead rows to do what it intends
to do.

n_ins_since_vacuum was introduced to indicate how many tuples a vacuum would touch on an insert-only table should vacuum be run now.  Autovacuum uses this value when determining whether a given relation should be vacuumed.

David J.

pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Summarizing indexes allowing single-phase VACUUM?
Next
From: Sami Imseih
Date:
Subject: Re: n_ins_since_vacuum stats for aborted transactions