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-10T14:01:05Z

Lists: pgsql-hackers

Attachments

v1-0001-Add-code-comment-for-ins_since_vacuum.patch (application/octet-stream) patch v1-0001
v1-0002-Clarify-when-aborted-and-committed-rows-are-track.patch (application/octet-stream) patch v1-0002

I created an entry for the July CF
https://commitfest.postgresql.org/patch/5691/

... and I realized I forgot to include David's code comment patch yesterday,
Reattaching both patches.


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