On Tue, Jan 26, 2010 at 05:12:51PM -0500, Greg Smith wrote:
> Hashimoto Yuya wrote:
> > Judging from the result, I could see that stats collector process
> > caused this unusually high CPU utilization rate.
> > I found similar problem at
> > http://archives.postgresql.org/pgsql-general/2008-06/msg0
Hashimoto Yuya wrote:
> Judging from the result, I could see that stats collector process
> caused this unusually high CPU utilization rate.
> I found similar problem at
> http://archives.postgresql.org/pgsql-general/2008-06/msg00934.php,
> although there seemed
> no clear cause proven nor the stat
Thanks,
> How large is $PGDATA/global/pgstat.stat ?
Unfortunately, the size of pgstat.stat was not taken when the CPU utilization
of the postgress process reached nearly 100%...
> If it's very large (many MB), try doing pg_stats_reset(). If that makes
> the stats collector CPU usage dr
> 8.3.3 is fairly old, they are up to 8.3.9 in that version. seee the
> release notes for each version from 8.3.4 to 8.3.9 to see what bugs were
> fixed...
> http://www.postgresql.org/docs/current/static/release.html
Thanks,
I was planning to update the postgres to the newer version, but
Hashimoto Yuya writes:
> [ lots of time spent by stats collector process ]
How large is $PGDATA/global/pgstat.stat ?
If it's very large (many MB), try doing pg_stats_reset(). If that makes
the stats collector CPU usage drop, consider an update to PG 8.4.x,
which is more efficient at dealing wit
Hashimoto Yuya wrote:
-Postgres version : "PostgreSQL 8.3.3 on i386-portbld-freebsd7.0,
compiled by GCC cc (GCC) 4.2.1 20070719 [FreeBSD]"
8.3.3 is fairly old, they are up to 8.3.9 in that version. seee the
release notes for each version from 8.3.4 to 8.3.9 to see what bugs were
fixed...
htt
Hello,
I observed the event that CPU utilization of the process related to postgres
records almost 100% for unknown reason. It would be appreciated if any of you
provide any information on this.
The following line is a part of the result of "ps -auxeww".
===
