Re: [GENERAL] postmaster deadlock while logging after syslogger exited

From: Andres Freund <andres(at)anarazel(dot)de>
To: David Pacheco <dap(at)joyent(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] postmaster deadlock while logging after syslogger exited
Date: 2017-12-04 20:23:20
Message-ID: 20171204202320.xaufivj3ik3gaqkh@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 generates the very large query strings only runs
> occasionally. Those strings are also not logged unless something's gone
> wrong.

FWIW, I'd like to see a report of this around the time the issue
occurred before doing anything further here.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2017-12-04 21:02:25 Re: Centos 6.9 and centos 7
Previous Message David Pacheco 2017-12-04 20:19:00 Re: [GENERAL] postmaster deadlock while logging after syslogger exited