| From: | Jim Nasby <jim(at)nasby(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Signaling of waiting for a cleanup lock? |
| Date: | 2014-04-14 22:39:02 |
| Message-ID: | 534C6386.5090200@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/14/14, 12:44 PM, Tom Lane wrote:
> Andres Freund<andres(at)2ndquadrant(dot)com> writes:
>> >On 2014-04-14 13:06:21 -0400, Tom Lane wrote:
>>> >>In particular I'm not sold on the use-case
>>> >>for being able to tell that a process is waiting without being able to
>>> >>tell what it's waiting for. I can figure that much out already.
>> >You can? How? It could also be io or something else that's problematic.
> If the process is not consuming any CPU time at all, it's waiting on
> something. (Now admittedly, that might be hard to tell remotely ---
> but Simon seems to be assuming you have access to "ps" output.)
Right... and then I always find myself wondering what it's actually waiting on. IO? lwlock? Something else?
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-04-14 22:51:23 | Re: PostgreSQL in Windows console and Ctrl-C |
| Previous Message | Jim Nasby | 2014-04-14 22:36:40 | Re: Signaling of waiting for a cleanup lock? |