pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Benjamin Krajmalnik <kraj@servoyant.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Problem with pgstat timneouts
Date: Thu, 22 Dec 2011 13:45:22 -0500
Message-ID: <17671.1324579522@sss.pgh.pa.us> (raw)
In-Reply-To: <F4E6A2751A2823418A21D4A160B689888CA5AE@fletch.stackdump.local>
References: <F4E6A2751A2823418A21D4A160B689888CA5A0@fletch.stackdump.local>
	<16795.1324576473@sss.pgh.pa.us>
	<F4E6A2751A2823418A21D4A160B689888CA5AE@fletch.stackdump.local>

"Benjamin Krajmalnik" <kraj@servoyant.com> writes:
> The only thing which I see when I run iostat is load on the drives every
> so often.  Mifd0 is the database, mifd1 is the pg_xlog.

Hmm.  Maybe checkpoints or something else saturating your drives for a
little while?  You might want to be more aggressive about smoothing out
checkpoints, cf
http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm
At the very least I'd enable checkpoint logging for awhile and see
if there seems to be any correlation to the response-time glitches.

			regards, tom lane

view thread (6+ messages)  latest in thread

Message-ID: <17671.1324579522@sss.pgh.pa.us>
Permalink:  ../17671.1324579522@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/17671.1324579522@sss.pgh.pa.us

copy link · copy postgr.es

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: tgl@sss.pgh.pa.us, kraj@servoyant.com
  Subject: Re: Problem with pgstat timneouts
  In-Reply-To: <17671.1324579522@sss.pgh.pa.us>

* 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