| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | 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> |
| Subject: | Re: display hot standby state in psql prompt |
| Date: | 2025-10-23 21:02:46 |
| Message-ID: | aPqX9gpmxzjFRRTG@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 23, 2025 at 10:03:54AM +0200, Jim Jones wrote:
> I believe that 'read/write' is more idiomatic than 'read-write' in this
> context. 'Read-only' works as a hyphenated adjective, and 'read/write'
> is typically treated as a paired label that indicates two distinct
> capabilities --- read and write. What do you think?
My first thought when looking at this thread/patch was that something like
"read-write" might be a bit long for a psql prompt. I probably would've
chosen something like "r" or "ro" for read-only and "rw" for read-write. I
suppose you could argue that those are more difficult to see, and this
seems particularly useful when you want to be sure that you won't
inadvertently write any data.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-10-23 21:35:58 | Re: [Proposal] Adding callback support for custom statistics kinds |
| Previous Message | Masahiko Sawada | 2025-10-23 21:00:50 | Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions |