Re: Add new option 'all' to pg_stat_reset_shared()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
Cc: bharath(dot)rupireddyforpostgres(at)gmail(dot)com, Andres Freund <andres(at)anarazel(dot)de>, boekewurm+postgres(at)gmail(dot)com, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add new option 'all' to pg_stat_reset_shared()
Date: 2023-11-13 05:55:19
Message-ID: ZVG6R0p_FvmCq1EL@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 13, 2023 at 01:15:14PM +0900, torikoshia wrote:
> I assume you have already taken this into account, but I think we should add
> the same documentation to the below patch for pg_stat_reset_slru():
>
> https://www.postgresql.org/message-id/CALj2ACW4Fqc_m%2BOaavrOMEivZ5aBa24pVKvoXRTmuFECsNBfAg%40mail.gmail.com

Yep, the DEFAULT value and the argument name should be documented in
monitoring.sgml.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2023-11-13 06:38:37 Re: Synchronizing slots from primary to standby
Previous Message Laurenz Albe 2023-11-13 05:53:29 Re: How to solve the problem of one backend process crashing and causing other processes to restart?