Re: Using ProcSignal to get memory context stats from a running backend

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Using ProcSignal to get memory context stats from a running backend
Date: 2017-12-15 02:34:14
Message-ID: CAMsr+YHGKinYA4QoEHpwo6=PxA5OoowUcWGo6+=wsmWe35rCdw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 15 December 2017 at 09:24, Greg Stark <stark(at)mit(dot)edu> wrote:

> Another simpler option would be to open up a new file in the log
> directory

... if we have one.

We might be logging to syslog, or whatever else.

I'd rather keep it simple(ish).

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2017-12-15 02:36:07 Re: pearltidy source code has been removed (pgindent)
Previous Message Andres Freund 2017-12-15 02:30:59 Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple