Thanks again for helping out.
On Mon, Dec 4, 2017 at 2:12 PM, Andres Freund wrote:
> On 2017-12-04 13:57:52 -0800, David Pacheco wrote:
> > On Mon, Dec 4, 2017 at 12:23 PM, Andres Freund
> wrote:
> > > FWIW, I'd like to see a report of this around the time the issue
> > > occurred before doing
On 2017-12-04 13:57:52 -0800, David Pacheco wrote:
> On Mon, Dec 4, 2017 at 12:23 PM, Andres Freund wrote:
> > FWIW, I'd like to see a report of this around the time the issue
> > occurred before doing anything further here.
> >
>
>
> This failure begins when this process exits, so the best you
On Mon, Dec 4, 2017 at 12:23 PM, Andres Freund wrote:
> Hi,
>
> On 2017-11-20 11:12:08 -0800, David Pacheco wrote:
> > $ ps -opid,rss,vsz,args -p 37627
> > PID RSS VSZ COMMAND
> > 37627 2980 14968 /opt/postgresql/9.2.4/bin/postgres -D /manatee/pg/data
> >
> > I'm not sure what we can infer fr
Hi,
On 2017-11-20 11:12:08 -0800, David Pacheco wrote:
> $ ps -opid,rss,vsz,args -p 37627
> PID RSS VSZ COMMAND
> 37627 2980 14968 /opt/postgresql/9.2.4/bin/postgres -D /manatee/pg/data
>
> I'm not sure what we can infer from that, as this is a different system,
> and the workload that genera
On Mon, Nov 20, 2017 at 11:12 AM, David Pacheco wrote:
> I understand if the community isn't interested in fixing this case if
> other users aren't seeing it much, but surely it's still a bug that this
> unusual case can result in a deadlock?
>
I've filed bug 14945 to cover this issue:
https://
Hi,
On 2017-11-20 11:12:08 -0800, David Pacheco wrote:
> > > This is a critical point. As far as I can tell, all that's necessary
> > > for this deadlock to occur is:
> > >
> > > - the syslogger is unable to make forward progress (e.g., because it
> > > segfaulted)
> >
> > This specific case I do
Thanks again for looking at this issue.
On Mon, Nov 20, 2017 at 10:34 AM, Andres Freund wrote:
> Hi,
>
> On 2017-11-20 10:13:57 -0800, David Pacheco wrote:
> > I expect what happened is that the syslogger process attempted to
> allocate
> > memory, failed because the system was low, and explicit
Hi,
On 2017-11-20 10:13:57 -0800, David Pacheco wrote:
> I expect what happened is that the syslogger process attempted to allocate
> memory, failed because the system was low, and explicitly exited. That's
> consistent with an exited process, no core file generated, and the "FATAL"
> "out
> of m
Responding to several points below.
Tom Lane wrote:
> David's report isn't too clear: did the syslogger process actually run
> out of memory and exit of its own volition after an ENOMEM, or did it get
> killed by the dreaded OOM killer? In either case, it's unclear whether
> it was really using a
