Re: iso-8859-1 Process DETAIL: Failed process was running: LISTEN dirty - Mailing list pgsql-admin

From David G. Johnston
Subject Re: iso-8859-1 Process DETAIL: Failed process was running: LISTEN dirty
Date
Msg-id CAKFQuwaZ=oX_2SYETdvHa39y1-V56LfaXwf2u5zxxbUwmghUCg@mail.gmail.com
Whole thread Raw
In response to Re: iso-8859-1 Process DETAIL: Failed process was running: LISTENdirty  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-admin


On Thursday, June 21, 2018, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
Jorge Daniel wrote:
> 2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:LOG:  server process (PID 235545) was terminated by signal 9: Killed
> 2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:DETAIL:  Failed process was running: LISTEN dirty
> 2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:LOG:  terminating any other active server processes

The "LISTEN dirty" is nice, but it has nothing to do with your problem.

If you are not aware of any programs or people at large on your
system that might "kill -9" harmless processes, you might have
fallen prey to the OOM killer.

Check your kernel log for message to confirm that.
That would mean that you have run out of memory.


My random guess would be someone did:

Begin;
Listen dirty;

Walks away...

Someone/thing else sees a long running transaction and kills it.

OOM is just as likely though the listen showing as running just seems odd to me.

David J.

pgsql-admin by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: iso-8859-1 Process DETAIL: Failed process was running: LISTEN dirty
Next
From: Wells Oliver
Date:
Subject: Reading on how materialized views are materialized?