Re: display hot standby state in psql prompt
| От | Jim Jones | 
|---|---|
| Тема | Re: display hot standby state in psql prompt | 
| Дата | |
| Msg-id | 508b6027-1077-45c2-8677-7a8205e51fd1@uni-muenster.de обсуждение исходный текст  | 
		
| Ответ на | Re: display hot standby state in psql prompt (Chao Li <li.evan.chao@gmail.com>) | 
| Ответы | 
                	
            		Re: display hot standby state in psql prompt
            		
            		 | 
		
| Список | pgsql-hackers | 
Hi Chao
On 30/10/2025 08:51, Chao Li wrote:
> I did a quick test, and found a problem. I shutdown the server, and “\c” reconnecting failed, but psql still show
“read/write”,which seems wrong:
 
> 
> "read/write"\c
> connection to server on socket "/tmp/.s.PGSQL.5432" failed: No such file or directory
>     Is the server running locally and accepting connections on that socket?
> Previous connection kept
I can see that a "read/write" prompt in this case sounds misleading, but
I am not entirely sure it is a problem. The message says "Previous
connection kept", which might suggest that the previous parameter values
are cached? See %p:
postgres=# \set PROMPT1 '[%p] # '
[1268754] # \c
connection to server on socket "/tmp/.s.PGSQL.5432" failed: No such file
or directory
        Is the server running locally and accepting connections on that
socket?
Previous connection kept
[1268754] #
The backend pid is still displayed, although the server is no longer
running.
 > Why wrap “unknown” in "_()” but not “read-only” and “read/write”?
It didn't occur to me that read-only and read/write needed translation,
but I guess you're right. I'll add to the next version.
Thanks for the review. Much appreciated!
Best, Jim
		
	В списке pgsql-hackers по дате отправления: