On Wed, 2006-11-08 at 21:46 -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)?
This one I can't answer.
>
> It would be a drag to be without pg_stat_activity on this system. The
> performance detriment is lessened in 8.2, correct?
Yes my understanding is work was done on 8.2 to help eliviate the issue.
Sincerely,
Joshua D. Drake
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
