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 Naga Appani
Subject Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby
Date
Msg-id CA+QeY+Duj7R7pCfXzmvJbAoKcwq41kvVp-wK2FRTfygA4EvVPw@mail.gmail.com
Whole thread
In response to Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
On Wed, Sep 23, 2026 at 7:06 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Mon, Sep 21, 2026 at 10:55:02AM -0500, Naga Appani wrote:
> > I lean toward ERROR over NULL, but not strongly.
>
> I'll go switch that to an error if called while RecoveryInProgress(),
> then.  Bonus points regarding the fact that we can reuse some of the
> existing error messages from xlogfuncs.c, meaning no extra translation
> required.
> --
> Michael
Thanks Michael, that matches what I had in v2 as well (same
errmsg/errhint pattern from xlogfuncs.c).

Thanks,
Naga

pgsql-hackers by date:

Previous
From: Ajin Cherian
Date:
Subject: Re: table-write trigger can bypass ATPrepChangePersistence
Next
From: Manu
Date:
Subject: Re: index prefetching