Re: BUG #6229: Postgresql crashes after: LOG: statistics buffer is full - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6229: Postgresql crashes after: LOG: statistics buffer is full
Date
Msg-id 28510.1317154325@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #6229: Postgresql crashes after: LOG: statistics buffer is full  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-bugs
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Max Kunz's message of mar sep 27 13:50:57 -0300 2011:
>> i have detected a problem after postgres logs "statistics buffer is full":
>> The database achieves farther on connections from the clients but no one
>> could process a statement and neither of the connection was closed.
>> It was also not possible to shutdown postgresql regularly.

> The 8.1 branch is no longer supported.  You need to upgrade, at least to
> 8.2; but since that's going to lose support just past December 2011, you
> should look into something more recent than that too.

FWIW, I suspect the problem is at a much deeper level and "statistics
buffer is full" is just a minor symptom.  If the stats buffer process is
stuck, that should really have no effect on the system other than
failure to deliver statistics updates.  Probably the reason why it's
reporting this is that the stats collector process is stuck, and perhaps
the underlying reason for that is also affecting regular backends.  But
there's not nearly enough info here to diagnose the true cause.

In any case I agree with Alvaro that 8.1.3 is horribly obsolete,
and you should at least update to the end of the 8.1 release branch
if you can't easily migrate to a supported branch.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #6229: Postgresql crashes after: LOG: statistics buffer is full
Next
From: Tom Lane
Date:
Subject: Re: BUG #6227: No arguments for COPY OIDS and HEADER