Re: iso-8859-1 Process DETAIL: Failed process was running: LISTEN dirty
| От | David G. Johnston |
|---|---|
| Тема | Re: iso-8859-1 Process DETAIL: Failed process was running: LISTEN dirty |
| Дата | |
| Msg-id | CAKFQuwZ_RhqukuV+YrhXTBhgo_6nE4qwM=FJxgY2VZw5-bDDdw@mail.gmail.com обсуждение исходный текст |
| Ответ на | iso-8859-1 Process DETAIL: Failed process was running: LISTEN dirty (Jorge Daniel <elgaita@hotmail.com>) |
| Список | pgsql-admin |
On Thursday, June 21, 2018, Jorge Daniel <elgaita@hotmail.com> wrote:
Hi guys, we're receiving this kind of Abnormal terminations :2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:LOG: server process (PID 235545) was terminated by signal 9: Killed2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:DETAIL: Failed process was running: LISTEN dirty2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:LOG: terminating any other active server processesDoes someone has information about "LISTEN DIRTY" as failed process, I've google it but no mention of this anywhere.
Kill 9 isn't abnormal, it's user initiated (usually anyway). Someone killed an open client session that had issued the LISTEN SQL command with a user-specific channel name of "dirty".
I'm unsure under what circumstances a session would be running a listen command long enough to be killed in this manner - but it might be normal as I have little experience with listen mechanics.
David J.
В списке pgsql-admin по дате отправления: