Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aHCMy-0006xh-1t for pgsql-performance@arkaria.postgresql.org; Thu, 07 Jan 2016 15:20:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aHCMx-0004Cu-FB for pgsql-performance@arkaria.postgresql.org; Thu, 07 Jan 2016 15:20:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aHCLK-0002Eb-S5 for pgsql-performance@postgresql.org; Thu, 07 Jan 2016 15:19:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aHCLH-0006kN-EO for pgsql-performance@postgresql.org; Thu, 07 Jan 2016 15:19:14 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u07FJ4Wf013262; Thu, 7 Jan 2016 10:19:04 -0500 From: Tom Lane To: Scott Rankin cc: Jim Nasby , "pgsql-performance@postgresql.org" Subject: Re: Queries intermittently slow In-reply-to: References: <2A061A33-9E7C-44ED-A8A4-411FE128A1C9@motus.com> <25400.1452093555@sss.pgh.pa.us> <7EC59C76-D8FF-4880-8A50-9F1195D5D00E@motus.com> <26050.1452094727@sss.pgh.pa.us> <27999.1452096879@sss.pgh.pa.us> <28587.1452097950@sss.pgh.pa.us> <568DE640.5070508@BlueTreble.com> Comments: In-reply-to Scott Rankin message dated "Thu, 07 Jan 2016 15:03:35 +0000" Date: Thu, 07 Jan 2016 10:19:04 -0500 Message-ID: <13261.1452179944@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Scott Rankin writes: > Any other ideas? If there's no lock waits, and the tables are static, it's difficult to arrive at any other conclusion but that the process is simply losing the CPU for long intervals. What else is going on on this box? Have you made any attempt to correlate the slow queries with spikes in load average, swap activity, etc? regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance