Re: n_ins_since_vacuum stats for aborted transactions

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: n_ins_since_vacuum stats for aborted transactions
Date: 2025-04-12 01:13:45
Message-ID: CAKFQuwY0fHcq1AvU+WMaPi175pbcbrA6rO1fpvUz=kWhHLTgkw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 11, 2025 at 5:19 PM Sami Imseih <samimseih(at)gmail(dot)com> wrote:

> > WFM. Though is there a reason to avoid adding the "why" of the
> exception for n_mod_since_analyze?
>
> I did think about that. I thought it will be understood that since
> this is a field that deals with ANALYZE,
> it will be understood that only committed changes matter here, and not
> worth adding more text to the
> description. but, maybe it's worth it?
>
>
Absent field questions I'm content to think it is sufficiently obvious or
discoverable for others.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2025-04-12 02:30:21 Re: TOAST versus toast
Previous Message Sami Imseih 2025-04-12 00:37:49 Re: stats.sql fails during installcheck on mac