From: Jérôme BENOIS <jerome.benois@argia-engineering.fr>
To: pgsql-admin@postgresql.org
Subject: Re: LOG: statistics buffer is full
Date: Fri, 23 Jun 2006 11:10:49 +0200
Message-ID: <1151053849.4506.498.camel@localhost.localdomain> (raw)
In-Reply-To: <F136E490-1E4F-4C3F-8A0A-957EA1836577@pervasive.com>
References: <1150961045.4506.308.camel@localhost.localdomain>
<F136E490-1E4F-4C3F-8A0A-957EA1836577@pervasive.com>
Hello,
Thanks Jim, i change stats_command_string=false and i wait but it's
works now :-)
Jérôme.
Le jeudi 22 juin 2006 à 21:00 -0500, Jim Nasby a écrit :
> On Jun 22, 2006, at 2:24 AM, Jérôme BENOIS wrote:
> > We use 7.4.6 version and now we have a bad performance on our
>
> You should upgrade to the latest 7.4 version.
>
> > production server. We detected several strange messages in a log
> > file :
> >
> > LOG: statistics buffer is full
> > LOG: statistics buffer is full
> > LOG: statistics buffer is full
> >
> > When i search on mailings list archive, i found a patch to increase
> > the
> > buffer size in src/include/pgstat.h
> >
> > -#define PGSTAT_RECVBUFFERSZ ((int) (1024 * sizeof(PgStat_Msg)))
> > +#define PGSTAT_RECVBUFFERSZ ((int) (16384 * sizeof(PgStat_Msg)))
> >
> > And when i look the same file on the subversion trunk, the
> > "PGSTAT_RECVBUFFERSZ" constant is defined in a new file :
> > src/backend/postmaster/pgstat.c but with a same value.
> >
> > Can you explain this statistics buffer problem ? And increase this
> > buffer size is a good resolution ?
>
> Do you have stats_command_string=on? If so, your best bet is probably
> to disable that, because it has a very high overhead (I've seen as
> much as over 50%). FWIW, Tom recently made changes in HEAD that
> essentially remove the overhead for using stats_command_string.
> --
> Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
> Pervasive Software http://pervasive.com work: 512-231-6117
> vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
>
>
>
Attachments:
signature.asc (application/pgp-signature, 188B) download
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: jerome.benois@argia-engineering.fr
Subject: Re: LOG: statistics buffer is full
In-Reply-To: <1151053849.4506.498.camel@localhost.localdomain>
References: <1150961045.4506.308.camel@localhost.localdomain> <F136E490-1E4F-4C3F-8A0A-957EA1836577@pervasive.com> <1151053849.4506.498.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