From: Benjamin Minshall <minshall@intellicon.biz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: stats collector process high CPU utilization
Date: Thu, 08 Feb 2007 16:16:32 -0500
Message-ID: <45CB9330.3000603@intellicon.biz> (raw)
In-Reply-To: <7994.1170960391@sss.pgh.pa.us>
References: <45CB5441.1040707@intellicon.biz>
<21013.1170955076@sss.pgh.pa.us>
<45CB5D06.7090004@intellicon.biz>
<7994.1170960391@sss.pgh.pa.us>
Tom Lane wrote:
>
> OK, I was trying to correlate it with post-8.2.0 patches but evidently
> that's the wrong tree to bark up. No, this isn't an expected behavior.
I talked with a co-worker and discovered that we went from 8.1.5 to
8.2.2, ran a few hours then went to 8.2.3 after the patch was released.
I do not know if the high utilization was a problem during the few
hours on 8.2.2.
> Is there anything unusual about your database (huge numbers of tables,
> or some such)?
Nothing unusual. I have a few databases of about 10GB each; the
workload is mostly inserts using COPY or parameterized INSERTS inside
transaction blocks.
> Can you gather some info about what it's doing?
> strace'ing the stats collector might prove interesting, also if you have
> built it with --enable-debug then oprofile results would be helpful.
I will gather some strace info later today when I have a chance to
shutdown the server.
Thanks.
--
Benjamin Minshall <minshall@intellicon.biz>
Senior Developer -- Intellicon, Inc.
http://www.intellicon.bizAttachments:
smime.p7s (application/x-pkcs7-signature, 5.1K) 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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: minshall@intellicon.biz, tgl@sss.pgh.pa.us
Subject: Re: stats collector process high CPU utilization
In-Reply-To: <45CB9330.3000603@intellicon.biz>
* 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