| From: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
|---|---|
| To: | 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> |
| Subject: | Re: display hot standby state in psql prompt |
| Date: | 2025-10-27 20:17:03 |
| Message-ID: | 171b207e-8fb4-44bb-b6a3-9a12c5a9625b@uni-muenster.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
Best, Jim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-10-27 20:29:37 | Re: Feature: psql - display current search_path in prompt |
| Previous Message | Euler Taveira | 2025-10-27 20:13:39 | Re: [PATCH] Add Windows support for backtrace_functions (MSVC only) |