pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Merlin Moncure <mmoncure@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Benjamin Minshall <minshall@intellicon.biz>
Cc: pgsql-performance@postgresql.org
Subject: Re: stats collector process high CPU utilization
Date: Fri, 2 Mar 2007 07:00:00 +0530
Message-ID: <b42b73150703011730s7c6d4aaeo8d9206eab2594329@mail.gmail.com> (raw)
In-Reply-To: <17817.1172789069@sss.pgh.pa.us>
References: <45CB5D06.7090004@intellicon.biz>
	<20070209142459.GB4253@alvh.no-ip.org>
	<24717.1171033699@sss.pgh.pa.us>
	<29832.1171036557@sss.pgh.pa.us>
	<45CCA0DB.2010903@intellicon.biz>
	<1116.1171038786@sss.pgh.pa.us>
	<45CCBF13.2000707@intellicon.biz>
	<16282.1172779976@sss.pgh.pa.us>
	<b42b73150703011358p7dfe77dft85ba7f3cdd3ce160@mail.gmail.com>
	<17817.1172789069@sss.pgh.pa.us>

On 3/2/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Merlin Moncure" <mmoncure@gmail.com> writes:
> > On 3/1/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> A further report led us to realize that 8.2.x in fact has a nasty bug
> >> here: the stats collector is supposed to dump its stats to a file at
> >> most every 500 milliseconds, but the code was actually waiting only
> >> 500 microseconds :-(.  The larger the stats file, the more obvious
> >> this problem gets.
>
> > I think this explains the trigger that was blowing up my FC4 box.
>
> I dug in the archives a bit and couldn't find the report you're
> referring to?

I was referring to this:
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01418.php

Even though the fundamental reason was obvious (and btw, I inherited
this server less than two months ago), I was still curious what was
making 8.2 blow up a box that was handling a million tps/hour for over
a year. :-)

merlin



view thread (27+ messages)  latest in thread

Message-ID: <b42b73150703011730s7c6d4aaeo8d9206eab2594329@mail.gmail.com>
Permalink:  ../b42b73150703011730s7c6d4aaeo8d9206eab2594329@mail.gmail.com/
Also on:    postgresql.org/message-id/b42b73150703011730s7c6d4aaeo8d9206eab2594329@mail.gmail.com

 · 

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-performance@postgresql.org
  Cc: mmoncure@gmail.com, tgl@sss.pgh.pa.us, minshall@intellicon.biz
  Subject: Re: stats collector process high CPU utilization
  In-Reply-To: <b42b73150703011730s7c6d4aaeo8d9206eab2594329@mail.gmail.com>
  References: <45CB5D06.7090004@intellicon.biz> <20070209142459.GB4253@alvh.no-ip.org> <24717.1171033699@sss.pgh.pa.us> <29832.1171036557@sss.pgh.pa.us> <45CCA0DB.2010903@intellicon.biz> <1116.1171038786@sss.pgh.pa.us> <45CCBF13.2000707@intellicon.biz> <16282.1172779976@sss.pgh.pa.us> <b42b73150703011358p7dfe77dft85ba7f3cdd3ce160@mail.gmail.com> <17817.1172789069@sss.pgh.pa.us> <b42b73150703011730s7c6d4aaeo8d9206eab2594329@mail.gmail.com>

* 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