Re: ps_status on fastpath

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ps_status on fastpath
Date: 2010-12-17 19:25:17
Message-ID: 4101.1292613917@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Tom Lane's message of vie dic 17 12:41:06 -0300 2010:
>> Hm, what about pgstat_report_activity()?

> I wasn't sure about that, because of the overhead, but now that I look
> at it, it's supposed to be cheaper than changing the ps_status in some
> cases, so I guess there's no harm.

Yeah, if we can afford a possible kernel call to set ps status, it
doesn't seem like pgstat_report_activity should be a problem. I'm
also of the opinion that more people look at pg_stat_activity than
ps output these days.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-12-17 19:25:24 Re: unlogged tables vs. GIST
Previous Message Pavel Stehule 2010-12-17 19:23:59 Re: proposal: FOREACH-IN-ARRAY (probably for 9.2?)