Re: n_ins_since_vacuum stats for aborted transactions

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(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-18 19:41:21
Message-ID: CAA5RZ0v1V8OzsW+WfQP70gYeV1UT4wbtaUQLZegNPA3riH_rzA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I can see it being confusing. What about this wording to make it more
> clear when the field is
> updated?

here are both of the changes in v4.

--
Sami Imseih
Amazon Web Services (AWS)

Attachment Content-Type Size
v4-0001-Clarify-when-aborted-rows-are-tracked-for-tuple-r.patch application/octet-stream 2.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-04-18 19:45:58 Re: disabled SSL log_like tests
Previous Message Sami Imseih 2025-04-18 19:05:04 Re: n_ins_since_vacuum stats for aborted transactions