pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: statistics buffer is full
Date: Wed, 08 Nov 2006 22:59:24 -0800
Message-ID: <1163055564.28784.59.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0611082145020.23695@discord.home.frostconsultingllc.com>
References: <Pine.LNX.4.64.0611081843120.23695@discord.home.frostconsultingllc.com>
	<1163042869.28784.55.camel@localhost.localdomain>
	<Pine.LNX.4.64.0611081927530.23695@discord.home.frostconsultingllc.com>
	<1163043819.28784.57.camel@localhost.localdomain>
	<Pine.LNX.4.64.0611082145020.23695@discord.home.frostconsultingllc.com>

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






view thread (14+ messages)  latest in thread

Message-ID: <1163055564.28784.59.camel@localhost.localdomain>
Permalink:  ../1163055564.28784.59.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1163055564.28784.59.camel@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jd@commandprompt.com, jeff@frostconsultingllc.com
  Subject: Re: statistics buffer is full
  In-Reply-To: <1163055564.28784.59.camel@localhost.localdomain>
  References: <Pine.LNX.4.64.0611081843120.23695@discord.home.frostconsultingllc.com> <1163042869.28784.55.camel@localhost.localdomain> <Pine.LNX.4.64.0611081927530.23695@discord.home.frostconsultingllc.com> <1163043819.28784.57.camel@localhost.localdomain> <Pine.LNX.4.64.0611082145020.23695@discord.home.frostconsultingllc.com> <1163055564.28784.59.camel@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox