Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id E5DD21131ED1 for ; Thu, 22 Dec 2011 14:45:39 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Rdne3-0001QV-Op for pgsql-admin@postgresql.org; Thu, 22 Dec 2011 18:45:40 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id pBMIjNQ5017672; Thu, 22 Dec 2011 13:45:23 -0500 (EST) To: "Benjamin Krajmalnik" cc: "pgsql-admin" Subject: Re: Problem with pgstat timneouts In-reply-to: References: <16795.1324576473@sss.pgh.pa.us> Comments: In-reply-to "Benjamin Krajmalnik" message dated "Thu, 22 Dec 2011 11:25:46 -0700" Date: Thu, 22 Dec 2011 13:45:22 -0500 Message-ID: <17671.1324579522@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -4.5 (----) X-Archive-Number: 201112/134 X-Sequence-Number: 38892 "Benjamin Krajmalnik" 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