From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-admin@postgresql.org
Subject: Re: Details about pg_stat_bgwriter
Date: Tue, 08 Jun 2010 19:46:30 +0200
Message-ID: <hulvlj$lq0$1@dough.gmane.org> (raw)
In-Reply-To: <4C0E7E3E.2070309@2ndquadrant.com>
References: <hulnta$mqe$1@dough.gmane.org>
<4C0E7E3E.2070309@2ndquadrant.com>
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
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-admin@postgresql.org
Cc: spam_eater@gmx.net
Subject: Re: Details about pg_stat_bgwriter
In-Reply-To: <hulvlj$lq0$1@dough.gmane.org>
* 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