| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(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: | 2025-11-08 08:57:13 |
| Message-ID: | ff77cec2-1358-4adb-ae04-ba6fa8a7f734@proxel.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/31/25 10:00 PM, Jim Jones wrote:
> Thoughts on this approach?
I am not a fan at all of introducing running a query when calculating
the prompt. Imagine if there are network issues or otherwise and in
general I imagine that the prompt can send a query would be highly
surprising to most users.
I personally lean towards that maybe we should keep it simple and go
back to the origins of the patch which just tried to show if it is a
standby or not given how complex it is to tell that we are in read-only
or not. The alternative would be to update the protocol so the client if
informed if a transaction is read-only or not but I do not think it
would be possible to convince people to update the protocol just for
psql. Maybe if some connection pooler would also be interest but I am
not sure what they would need this for.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-11-08 09:40:36 | Re: [Patch] Windows relation extension failure at 2GB and 4GB |
| Previous Message | Andreas Karlsson | 2025-11-08 08:09:55 | Re: ago(interval) → timestamptz |