Request a Demo
Home   >   mailing lists

Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby
Date
Msg-id arG2Bz60u75sfquj@paquier.xyz
Whole thread
In response to Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby  (Naga Appani <nagnrik@gmail.com>)
List pgsql-hackers
Tree view 
On Mon, Sep 21, 2026 at 10:55:02AM -0500, Naga Appani wrote:
> AFAICS none of this is really actionable on a standby either way, since
> freezing and vacuum are only actionable on the primary. An error seems
> more honest than returning numbers that look real but don't drive any
> decision. Could be missing a use case though, please let me know what you
> think.

Yeah, I'd just choose an error at this stage rather than trying to
provide partially-true numbers.  If somebody is interested in
providing these numbers on a standby, that could always be done later
on.
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Support for 8-byte TOAST values, round two
Next
From: Sami Imseih
Date:
Subject: Re: Proposal: expose heavyweight lock wait start time in pg_stat_activity