From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: statistics buffer is full |
Date: | 2006-11-09 07:21:46 |
Message-ID: | 20061109072145.GI90133@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Nov 08, 2006 at 09:46:48PM -0800, Jeff Frost wrote:
> On Wed, 8 Nov 2006, Joshua D. Drake wrote:
>
> >>hah! Does that mean it's just the buffering for pg_stat_activity and not
> >>for
> >>planner statistics? That doesn't make me feel too bad in this case.
> >
> >Yeah it is nothing to worry about, however turning it off is certainly a
> >performance benefit.
> >
>
> So, then the next question: is that error because the command string was
> too long or because there were too many command strings in the buffer at
> once (i.e. it got backed up a bit and filled)?
IIRC, (in 8.1) the same amount of data is shuffled through the stats
system for every command, so it'd be an issue of too many messages.
> It would be a drag to be without pg_stat_activity on this system. The
> performance detriment is lessened in 8.2, correct?
Correct. Performance of updating the info for ps was also improved,
iirc.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Shellam (Mailing Lists) | 2006-11-09 09:53:57 | Re: Checkpoint Location Format |
Previous Message | Jim C. Nasby | 2006-11-09 07:15:49 | Re: Use Jobs |