Re: Feature: psql - display current search_path in prompt
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Chao Li <li.evan.chao@gmail.com>
Cc: Florents Tselai <florents.tselai@gmail.com>, Jim Jones <jim.jones@uni-muenster.de>, Jelte Fennema-Nio <postgres@jeltef.nl>, Lauri Siltanen <lauri.siltanen@gmail.com>, pgsql-hackers@postgresql.org
Date: 2025-10-28T17:21:15Z
Lists: pgsql-hackers
Attachments
On Tue, Oct 28, 2025 at 09:08:36AM +0800, Chao Li wrote:
>> On Oct 28, 2025, at 04:29, Nathan Bossart <nathandbossart@gmail.com> wrote:
>> Here is what I have staged for commit. I ended up simplifying the patch a
>> bit. In particular, I thought better of the question mark business. It
>> looks like we ordinarily just skip values that can't be found, and an empty
>> search_path will appear as "" (two double-quotes), so you can still
>> distinguish empty versus not-available.
>
> +1, I like this idea.
Actually, I take it back. The following command to empty the search_path
will cause %S to be replaced with nothing, in which case you can't
distinguish empty versus not-reported.
SELECT pg_catalog.set_config('search_path', '', false);
So, I've added the question mark back.
--
nathan
Commits
-
Add psql PROMPT variable for search_path.
- b3ce55f413cd 19 (unreleased) landed
-
doc PG 18 relnotes: add AFTER trigger user change item
- 73e26cbeb592 18.0 cited