Re: SIGTERM/FATAL error
От | Bruce Momjian |
---|---|
Тема | Re: SIGTERM/FATAL error |
Дата | |
Msg-id | 200103120108.UAA23989@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: SIGTERM/FATAL error (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: SIGTERM/FATAL error
|
Список | pgsql-hackers |
> Bruce Momjian <pgman@candle.pha.pa.us> writes: > >> This is a non-improvement. Please reverse it. SIGTERM would only be > >> sent to a backend if the database system were in fact shutting down. > > > But why say the system is shutting down if the backend is shutting down. > > Seems the postmaster should say system shutting down and each backend > > should say it is shutting itself down. The way it is now, don't we get > > a "system shutting down" message for every running backend? > > You are failing to consider that the primary audience for this error > message is not the system log, but the clients of the backends. They > are going to see only one message, and they are going to want to know > *why* their backend shut down. Oops, I get it now. Makes perfect sense. Thanks. I am using the SIGTERM in my administration application to allow administrators to kill individual backends. That is why I noticed the message. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: