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)?
Yeah, it got backed up. It's an UDP socket and it's having trouble
keeping up. Disabling stats_command_string removes the higher producer
of "statistics" traffic, and the price you pay for it is that queries
don't show up in pg_stat_activity. You can still see the tags in ps
though, and of course you'll have them in the log if you enabled that.
> It would be a drag to be without pg_stat_activity on this system. The
> performance detriment is lessened in 8.2, correct?
Yes, by not using the UDP socket to transmit the command string in the
first place. They are now just stored in memory, which is considerably
faster.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.