pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brian Fehrle <brianf@consistentstate.com>
To: pgsql-admin@postgresql.org
Subject: Hot standby having high requested checkpoints?
Date: Tue, 28 Feb 2012 15:53:20 -0700
Message-ID: <4F4D5AE0.9020204@consistentstate.com> (raw)

Hi all,

I have two PostgreSQL 9.0.5 clusters, one is a master and the other is a 
hot standby via streaming replication. I'm monitoring some stats on each 
and I'm noticing something very odd. On the master, I get between 2 and 
4 requested checkpoints per hour, but on the hot standby I'm seeing 
between 200 and 300 requested checkpoints per hour.

Both boxes are the same specs, and have the same following config 
parameters:
              name             | setting
------------------------------+---------
  bgwriter_delay               | 200
  bgwriter_lru_maxpages        | 350
  bgwriter_lru_multiplier      | 2
  checkpoint_completion_target | 0.5
  checkpoint_segments          | 256
  checkpoint_timeout           | 1800


Is there any reason why I would be seeing this type of behavior on the 
hot standby? Is it the standard type of behavior on a hot standby that 
I'm only now noticing?

Thanks in advance,
- Brian F

view thread (7+ messages)  latest in thread

Message-ID: <4F4D5AE0.9020204@consistentstate.com>
Permalink:  ../4F4D5AE0.9020204@consistentstate.com/
Also on:    postgresql.org/message-id/4F4D5AE0.9020204@consistentstate.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: brianf@consistentstate.com
  Subject: Re: Hot standby having high requested checkpoints?
  In-Reply-To: <4F4D5AE0.9020204@consistentstate.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox