Re: [HACKERS] Bgwriter behavior

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Bgwriter behavior
Date: 2005-01-04 08:36:20
Message-ID: 1104827780.22450.6.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Mon, 2005-01-03 at 19:14 -0500, Bruce Momjian wrote:
> Simon Riggs wrote:
> > Here's my bgwriter instrumentation patch, which gives info that could
> > allow the bgwriter settings to be tuned.
>
> Uh, what does this do exactly? Add additional logging output?
>

Produces output like this...

DEBUG:ARC T1target= 45 B1len= 4954 T1len= 40 T2len= 4960 B2len= 46
DEBUG:ARC total = 98% B1hit= 0% T1hit= 0% T2hit= 98% B2hit= 0%
DEBUG:ARC buffer dirty misses= 22% (wasted= 0); cleaned= 4494

when you have debug_shared_buffers (= n) set
and you have server messages DEBUG1 available.

The last line of log output has been replaced by this version.

--
Best Regards, Simon Riggs

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hans-Jürgen Schönig 2005-01-04 09:01:28 Re: Implementing RESET CONNECTION ...
Previous Message Karel Zak 2005-01-04 08:08:40 Re: Implementing RESET CONNECTION ...

Browse pgsql-patches by date

  From Date Subject
Next Message Hans-Jürgen Schönig 2005-01-04 09:01:28 Re: Implementing RESET CONNECTION ...
Previous Message Mark Kirkwood 2005-01-04 08:34:32 Re: Another Plpgsql trigger example - summary table