Re: display hot standby state in psql prompt

From: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Andreas Karlsson <andreas(at)proxel(dot)se>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Subject: Re: display hot standby state in psql prompt
Date: 2026-01-23 16:05:41
Message-ID: d81c08f6-1a4f-48ee-b1ff-e78b145c9e12@uni-muenster.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Fujii

On 12/11/2025 04:48, Fujii Masao wrote:
> I'm fine with the initial proposal. I think showing whether the connected
> server is a primary or standby in the prompt would be helpful when managing
> multiple servers. OTOH, I'm not sure how useful it would be to display
> whether the current transaction is read-only.
>
> That said, this is just my view, so I'd like to hear what others think.

Since we haven't heard any objections from the other reviewers, do you
think we should switch back to the initial "primary" or "standby" proposal?

Best, Jim

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Srirama Kucherlapati 2026-01-23 16:11:25 RE: AIX support
Previous Message Tom Lane 2026-01-23 15:50:49 Re: Auto-tune shared_buffers to use available huge pages