Re: Separating bgwriter and checkpointer

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Separating bgwriter and checkpointer
Date: 2011-10-19 10:36:08
Message-ID: CAHGQGwEm+S+dOUwix0RjyyOh1rmUjXTPCscv-q5DgzEEj2sQ8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 18, 2011 at 10:18 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Any reason or objection to committing this patch?

The checkpointer doesn't call pgstat_send_bgwriter(), but it should.
Otherwise, some entries in pg_stat_bgwriter will never be updated.

If we adopt the patch, checkpoint is performed by checkpointer. So
it looks odd that information related to checkpoint exist in
pg_stat_bgwriter. We should move them to new catalog even if
it breaks the compatibility?

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marti Raudsepp 2011-10-19 11:35:34 [PATCH] Deferrable unique constraints vs join removal -- bug?
Previous Message Kohei KaiGai 2011-10-19 10:35:49 Re: [v9.2] Fix Leaky View Problem