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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Naga Appani <nagnrik(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Noah Misch <noah(at)leadboat(dot)com>
Subject: Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby
Date: 2026-09-21 22:56:08
Message-ID: arG2Bz60u75sfquj@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-09-21 22:58:05 Re: Proposal: expose heavyweight lock wait start time in pg_stat_activity
Previous Message Michael Paquier 2026-09-21 22:53:17 Re: Support for 8-byte TOAST values, round two