Re: display hot standby state in psql prompt

On Tue, Oct 28, 2025 at 6:00 AM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>
> On Mon, Oct 27, 2025 at 09:17:03PM +0100, Jim Jones wrote:
> > On 27/10/2025 17:23, Nathan Bossart wrote:
> >> This was briefly mentioned upthread, but I'm a little concerned that this
> >> doesn't respond to commands like SET TRANSACTION READ ONLY. I wonder if we
> >> should mark transaction_read_only as GUC_REPORT and use that instead. FWIW
> >> I see that we marked search_path as GUC_REPORT somewhat recently (see
> >> commit 28a1121).
> >
> > You're right, it doesn't. I like the idea, but I'm not sure how to
> > integrate a transaction-scoped variable into this feature. Would that
> > mean we also need to change the reset mechanism for GUC_REPORT variables
> > when the transaction ends?

If we mark transaction_read_only as GUC_REPORT, wouldn't the reset value
be sent automatically at the end of the transaction? It seems like we wouldn't
need any new mechanism for that. However, the downside might be that
more ParameterStatus messages would be sent, potentially adding overhead.

Regards,

--
Fujii Masao