Re: [HACKERS] psql casts aspersions on server reliability
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] psql casts aspersions on server reliability |
Дата | |
Msg-id | ZV6Yvb5mu5VDRkfl@momjian.us обсуждение исходный текст |
Ответ на | Re: psql casts aspersions on server reliability (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] psql casts aspersions on server reliability
|
Список | pgsql-hackers |
On Wed, Sep 28, 2016 at 09:14:41AM -0400, Tom Lane wrote: > Robert Haas <robertmhaas@gmail.com> writes: > > psql tends to do things like this: > > rhaas=# select * from pg_stat_activity; > > FATAL: terminating connection due to administrator command > > server closed the connection unexpectedly > > This probably means the server terminated abnormally > > before or while processing the request. > > > Basically everything psql has to say about this is a lie: > > I cannot get terribly excited about this. What you seem to be proposing > is that psql try to intuit the reason for connection closure from the > last error message it got, but that seems likely to lead to worse lies > than printing a boilerplate message. > > I could go along with just dropping the last sentence ("This probably...") > if the last error we got was FATAL level. I don't find "unexpectedly" > to be problematic here: from the point of view of psql, and probably > of its user, the shutdown *was* unexpected. I looked at this thread from 2016 and I think the problem is the "abnormally" word, since if the server was shutdown by the administrator (most likely), it isn't abnormal. Here is a patch to remove "abnormally". -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.
Вложения
В списке pgsql-hackers по дате отправления: