Horton

Re: Feature: psql - display current search_path in prompt

Chao Li <li.evan.chao@gmail.com>

View thread View on postgr.es
From: Chao Li <li.evan.chao@gmail.com>
To: Nathan Bossart <nathandbossart@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-28T01:08:36Z
Lists: pgsql-hackers 

> 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.

V4 looks good to me.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

Commits

  1. Add psql PROMPT variable for search_path.

  2. doc PG 18 relnotes: add AFTER trigger user change item