Re: Design of pg_stat_subscription_workers vs pgstats

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Design of pg_stat_subscription_workers vs pgstats
Date: 2022-02-28 03:50:11
Message-ID: CAA4eK1LJwdjC=Gfzi4hBv9qeiZejqkb5nRaC7qNN201YVMWbLQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 28, 2022 at 8:59 AM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
>
> 2. doc/src/sgml/monitoring.sgml
>
> + Resets statistics for a single subscription shown in the
> + <structname>pg_stat_subscription_stats</structname> view to zero. If
> + the argument is <literal>NULL</literal>, reset statistics for all
> + subscriptions.
> </para>
>
> SUGGESTED (simpler description, more similar to pg_stat_reset_replication_slot)
> Reset statistics to zero for a single subscription. If the argument is
> <literal>NULL</literal>, reset statistics for all subscriptions.
>

As discussed, it is better to keep the view name in this description
important as we have another view (pg_stat_susbcription) as well. So,
I am planning to retain the current wording.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-02-28 03:57:18 Re: Design of pg_stat_subscription_workers vs pgstats
Previous Message Amit Kapila 2022-02-28 03:46:59 Re: Commitfest manager for 2022-03