Re: [HACKERS] Overhead for stats_command_string et al, take 2 - Mailing list pgsql-patches

From Tom Lane
Subject Re: [HACKERS] Overhead for stats_command_string et al, take 2
Date
Msg-id 2141.1151343124@sss.pgh.pa.us
Whole thread Raw
List pgsql-patches
Bruce Momjian <bruce@momjian.us> writes:
> Tom Lane wrote:
>> Something that might also be interesting is an option to suppress
>> per-command ps_status reporting.  On machines where updating ps status
>> takes a kernel call, there's now a pretty good argument why you might
>> want to turn that off and rely on pg_stat_activity instead.

> OK, can I get a timing report from someone with the title on/off that
> shows a difference?

IIRC, newer BSDen use a kernel call for this, so you should be able to
measure it on your own machine.  Just tweak ps_status.c to force it to
select PS_USE_NONE instead of PS_USE_SETPROCTITLE to generate a
comparison case.  I'll try it on my old HPUX box too.

            regards, tom lane

pgsql-patches by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: MS-VC build patch
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Overhead for stats_command_string et al, take 2