Re: PATCH: regular logging of checkpoint progress

From: "Tomas Vondra" <tv(at)fuzzy(dot)cz>
To: "Noah Misch" <noah(at)2ndQuadrant(dot)com>
Cc: "Tomas Vondra" <tv(at)fuzzy(dot)cz>, "Greg Smith" <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PATCH: regular logging of checkpoint progress
Date: 2011-08-27 13:57:16
Message-ID: 240e9c7a3e0deb664908c4bd07a4a01e.squirrel@sq.gransy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 27 Srpen 2011, 6:01, Noah Misch wrote:
> On Fri, Aug 26, 2011 at 10:46:33AM +0200, Tomas Vondra wrote:
>> 1. collect pg_stat_bgwriter stats
>> 2. run pgbench for 10 minutes
>> 3. collect pg_stat_bgwriter stats (to compute difference with (1))
>> 4. kill the postmaster
>>
>> The problem is that when checkpoint stats are collected, there might be
>> a
>> checkpoint in progress and in that case the stats are incomplete. In
>> some
>> cases (especially with very small db blocks) this has significant impact
>> because the checkpoints are less frequent.
>
> Could you remove this hazard by adding a step "2a. psql -c CHECKPOINT"?

I already do that, but it really does not solve the issue. It just aligns
the first expected 'timed' checkpoint, it does not solve the problem with
in-progress checkpoints unless the runs behave exactly the same (and
that's the boring case).

Tomas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-08-27 14:19:59 Re: [COMMITTERS] pgsql: Avoid locale dependency in expected output.
Previous Message Jeff MacDonald 2011-08-27 13:29:16 Re: Inputting relative datetimes