Skip site navigation (1) Skip section navigation (2)

Re: Checkpointer vs pg_stat_bgwriter

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Subject: Re: Checkpointer vs pg_stat_bgwriter
Date: 2012-02-28 06:06:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, Feb 27, 2012 at 4:24 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> Hi!
> I admit to not having actually tested this since I don't have a good
> cluster to test it on right now, but from what I can tell the code in
> the new checkpointer process only sends statistics to the collector
> once the checkpoint is finished (checkpointer.c, line 549). The 9.1
> and earlier sent this every time they entered a delay state (in
> BgWriterNap() called from CheckpointWriteDelay()).
> So in 9.1 and earlier we could see how a checkpoint wrote things as it
> was running, but in 9.2 we'll get it all as one big block at the end
> of the checkpoint - which can be a lot later in the spread case.
> Am I reading the code right?
> And if so, was this an intentional change, and if so why? To me it
> seems like a loss of functionality that should be fixed..

I agree that this should be fixed.


Fujii Masao
NTT Open Source Software Center

In response to

pgsql-hackers by date

Next:From: Ants AasmaDate: 2012-02-28 06:15:11
Subject: Re: Initial 9.2 pgbench write results
Previous:From: Josh KupershmidtDate: 2012-02-28 05:05:13
Subject: misleading error message from connectMaintenanceDatabase()

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group