To: pgsql-admin@postgresql.org
connect(): No such file or directory
From: Thomas Kellerer <spam_eater@gmx.net>
Subject: Re: Details about pg_stat_bgwriter
Date: Tue, 08 Jun 2010 19:46:30 +0200
Lines: 20
Message-ID: <hulvlj$lq0$1@dough.gmane.org>
References: <hulnta$mqe$1@dough.gmane.org> <4C0E7E3E.2070309@2ndquadrant.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@dough.gmane.org
X-Gmane-NNTP-Posting-Host: ppp-188-174-93-160.dynamic.mnet-online.de
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de;
	rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.5.666
In-Reply-To: <4C0E7E3E.2070309@2ndquadrant.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201006/73
X-Sequence-Number: 34851

Greg Smith wrote on 08.06.2010 19:30:
> Thomas Kellerer wrote:
>> If I want to identify a possible bottleneck with the bgwriter, for
>> what kind of numbers do I need to watch out?
> You don't much with a single snapshot of pg_stat_bgwriter data. Try
> saving this instead:
>
> select *,now() from pg_stat_bgwriter;
>
> And then take another snapshot at least a few hours later, preferably
> the next day. With two snapshots and timestamps on them, then it's
> possible to make some sense of the numbers.
>
Thanks for the answer.

After taking a few snapshots, what would I look for?

Regards
Thomas