| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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 19:11:30 |
| Message-ID: | 553A9562.7010801@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/24/15 6:29 AM, Robert Haas wrote:
> 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.
I more often am wondering what a running backend is doing OS-wise, but
being able to see what happened when it finished would definitely be
better than what's available now.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-04-24 19:20:13 | Re: Typo in a comment in set_rel_size() |
| Previous Message | Alvaro Herrera | 2015-04-24 19:04:03 | Re: Feedback on getting rid of VACUUM FULL |