Re: Write-heavy pg_stats_collector on mostly idle server

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>
Cc: jd(at)commandprompt(dot)com, pgsql-performance(at)postgresql(dot)org
Subject: Re: Write-heavy pg_stats_collector on mostly idle server
Date: 2011-02-08 01:39:45
Message-ID: 4D509EE1.4070305@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


> Ooops.
> It looks like you are right, see ./src/backend/postmaster/pgstat.c
>
> 3c2313f4 (Tom Lane 2008-11-03 01:17:08 +0000 2926)
> if (last_statwrite < last_statrequest)
> 70d75697 (Magnus Hagander 2008-08-05 12:09:30 +0000 2927)
> pgstat_write_statsfile(false);

This is a different issue. This is happening because we have a bunch of
databases (25 to 35) and as a result autovacuum is requesting the stats
file rather frequently. And autovacuum for whatever reason won't accept
a stats file more than 10ms old, so it pretty much rewrites the stats
file on every request.

At least, that's my reading of it after poking around and talking to
Gierth.

It seems like that 10ms window for autovac is way too small.

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message felix 2011-02-08 03:17:46 Re: Really really slow select count(*)
Previous Message Sylvain Rabot 2011-02-08 00:14:58 Indexes with condition using immutable functions applied to column not used