Re: Report bytes and transactions actually sent downtream - Mailing list pgsql-hackers

From Ashutosh Sharma
Subject Re: Report bytes and transactions actually sent downtream
Date
Msg-id CAE9k0PmBdxB_bpWAT9V9TqkKzRCbPTOBTU3f5OtRVhZ64VKFhw@mail.gmail.com
Whole thread
In response to Re: Report bytes and transactions actually sent downtream  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Report bytes and transactions actually sent downtream
Re: Report bytes and transactions actually sent downtream
List pgsql-hackers
Hi,

On Mon, Mar 16, 2026 at 12:20 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Mon, Mar 16, 2026 at 08:55:17AM +0530, Ashutosh Bapat wrote:
> > I would post two patches
> > 1. To introduce the new column sent_bytes + clarify total_bytes in the
> > context of sent_bytes. We should consider this patch for committing.
>
> Sounds to me like two patches: one for the new column, a second for
> the docs of the existing columns.  Could somebody send these patches?
> I would be OK to look at them once posted, driving things for this CF.
>

PFA patches:

1) v20260316-0001-Report-downstream-sent-bytes-in-pg_stat_replication_.patch:

This patch introduces sent_bytes to report the amount of data sent
downstream. It documents sent_bytes in a way that it clarifies how
sent_bytes differs from total_bytes, without modifying the existing
documentation for total_bytes or total_txns. The patch is purely
additive and does not alter any existing documentation.

2) v20260316-0002-Report-output-plugin-statistics-in-pg_stat_replicati.patch:

This patch adds a couple of more metrics to report the amount of
changes filtered out by the output plugin, as well as the total number
of transactions sent downstream.

--
With Regards,
Ashutosh Sharma.

Attachment

pgsql-hackers by date:

Previous
From: Dmitrii Bondar
Date:
Subject: Re: Pgbench: remove synchronous prepare
Next
From: wenhui qiu
Date:
Subject: Re: Report oldest xmin source when autovacuum cannot remove tuples