Re: n_ins_since_vacuum stats for aborted transactions

Sami Imseih <samimseih@gmail.com>

From: Sami Imseih <samimseih@gmail.com>

To: David Rowley <dgrowleyml@gmail.com>

Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Mark Dilger <mark.dilger@enterprisedb.com>, Euler Taveira <euler@eulerto.com>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-04-18T19:41:21Z

Lists: pgsql-hackers

Attachments

v4-0001-Clarify-when-aborted-rows-are-tracked-for-tuple-r.patch (application/octet-stream) patch v4-0001

> 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)

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add code comment explaining ins_since_vacuum and aborted inserts
- 530050d8d285 18.0 landed
Trigger autovacuum based on number of INSERTs
- b07642dbcd8d 13.0 cited