Re: Publish checkpoint timing and sync files summary data to pg_stat_bgwriter

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Publish checkpoint timing and sync files summary data to pg_stat_bgwriter
Date: 2012-01-23 02:08:55
Message-ID: CA+TgmoZUGvBFk5b7QTcX82pwjHeUSb+Q83YPp_UrZLOJaFzj0A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jan 21, 2012 at 6:32 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> I'm finding the backend_writes column pretty unfortunate.  The only
> use I know of for it is to determine if the bgwriter is lagging
> behind.  Yet it doesn't serve even this purpose because it lumps
> together the backend writes due to lagging background writes, and the
> backend writes "by design" due to the use buffer access strategy
> during bulk inserts.

+1 for separating those.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-01-23 02:17:09 Re: Next steps on pg_stat_statements normalisation
Previous Message Robert Haas 2012-01-23 02:06:39 Re: Removing freelist (was Re: Should I implement DROP INDEX CONCURRENTLY?)