As it turns out, you can use that same mechanism to customize the xterm titles from within psql. It might not be completely clear why that is necessary. After all, if you have customized the xterm titles in your shell, say to show the name of the command currently running, then it would already show something like "psql somedb" when you are using psql. The trick, or perhaps danger, with that is that if you use commands like \c or SET SESSION AUTHORIZATION in psql, then your connection parameters change, but the shell doesn't update the xterm title. This had me confused more than once now.
The control sequence to change the xterm title is ESC]0;stringBEL, where ESC is \033 and BEL is \007. In psql prompt language, this becomes [%033]0;string%007%]. Add that somewhere to your prompt (doesn't really matter where, as it won't be printed). Say you are using the default prompt (boring!) and want to show "psql dbname" in the xterm window title when logged in to PostgreSQL, then put this into your ~/.psqlrc:
\set PROMPT1 '%[%033]0;psql %/%007%]%/%R%# '
Note: If you don't have your shell to set up to update the xterm title, then the title set by psql will remain after you quit psql. That might be even more confusing, so don't try this if you don't have your shell set up for this.
If you have other fun and/or useful ideas for the psql prompt, please share them in the comments.
I've been using this for my normal shell for decades now to keep the hostname and path on the title bar. I never even thought to use it within psql. Clever.
ReplyDeleteAlso note that the MacOS X terminal app honors the same escape sequences, so it works there as well.
Really useful info.
ReplyDeleteI think you missed one % just before the 7.
\set PROMPT1 '%[%033]0;psql %/%7%]%/%R%# '
At least thats what I had to do on my Fedora.
- Gurjeet
The blogger software ate those characters somehow. It looks correct now. Thanks.
ReplyDeleteWhen I use the above syntax, my psql (v 8.2.15) just hangs and nothing happens. The only other action I am allowed to perform is press ^Z and come of of the program (^C also does not work!)
ReplyDeleteIf I exclude the enclosures [% and %] , I see the PROMPT1 changes take effect. This however does not show older multiline queries properly when up arrow is pressed. The queries appear garbled even though they run fine.
(BTW, I observed similar behavior in bash when I added color to my bash prompt. I was able to fix that problem by defining the colors as variables and using them in PS1 setting. I wonder if the 2 problems are related)
Anyone faced a similar issue?
@Shreyas: Hard to say. You should file a bug report. Except that 8.2 is EOL, so upgrade first.
ReplyDelete