I wrote:
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.
On HPUX, I get a median
Bruce Momjian [EMAIL PROTECTED] 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
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Seeing stats_command_string with almost zero overhead is great news!
Should we remove that setting and just have it enabled all
the time?
If you don't need it, you shouldn't have to pay any overhead for it,
I think. One could make
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Yep, I see 8% here. I will add a patch to allow the ps display to be
turned off.
I think we'd still want a backend to set the PS display once with its
identification data (user/DB name and client address). It's just the
transient
