Postgres Pro
Downloads
Home   >   mailing lists

Re: Using ProcSignal to get memory context stats from a running backend - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Using ProcSignal to get memory context stats from a running backend
Date
Msg-id CA+TgmobFuwb64xQ0uuDVcq_cVBKHjfC46mTY9DwNNLkiyhBgHw@mail.gmail.com
Whole thread Raw
In response to Re: Using ProcSignal to get memory context stats from a running backend  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Using ProcSignal to get memory context stats from a running backend
List pgsql-hackers
Tree view 
On Thu, Dec 14, 2017 at 9:34 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
> On 15 December 2017 at 09:24, Greg Stark <stark@mit.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).

+1.  I still think just printing it to the log is fine.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Proposal: Local indexes for partitioned table
Next
From: David Rowley
Date:
Subject: Re: [HACKERS] Proposal: Local indexes for partitioned table