Re: adding more information about process(es) cpu and memory usage

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, hlinnaka <hlinnaka(at)iki(dot)fi>, Radovan Jablonovsky <radovan(dot)jablonovsky(at)replicon(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: adding more information about process(es) cpu and memory usage
Date: 2015-04-24 11:29:47
Message-ID: CA+TgmoanwcOuWHGwPp5KYwzZzFEOkMqX=hGHQE8H7jq+fSqCaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 23, 2015 at 9:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The reason nobody's gotten around to that in the last fifteen years is
> that per-process rusage isn't actually all that interesting; there's
> too much that happens in background daemons, for instance.

There's *some* stuff that happens in background daemons, but if you
want to measure user and system time consume by a particularly query,
this would actually be a pretty handy way to do that, I think.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-04-24 11:50:46 Re: Improving vacuum/VM/etc
Previous Message Stephen Frost 2015-04-24 11:24:59 Re: [committers] pgsql: RLS fixes, new hooks, and new test module