Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bK2qm-0007K6-J7 for pgsql-performance@arkaria.postgresql.org; Mon, 04 Jul 2016 12:19:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bK2ql-0007xe-KF for pgsql-performance@arkaria.postgresql.org; Mon, 04 Jul 2016 12:19:43 +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_2) id 1bK2qk-0007wt-Fn for pgsql-performance@postgresql.org; Mon, 04 Jul 2016 12:19:42 +0000 Received: from [2607:ff10:c5:506:225:90ff:feab:5c2e] (helo=gourmet8.spamgourmet.com) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) id 1bK2qc-0001vJ-U2 for pgsql-performance@postgresql.org; Mon, 04 Jul 2016 12:19:41 +0000 Received: from spamgourmet by gourmet7.spamgourmet.com with local (Exim 4.80) (envelope-from ) id 1bK2qZ-00017g-Bp for pgsql-performance@postgresql.org; Mon, 04 Jul 2016 12:19:31 +0000 Received: from mail-lf0-f54.google.com ([209.85.215.54]) by gourmet7.spamgourmet.com with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1bK2qZ-00017D-1N for ; Mon, 04 Jul 2016 12:19:31 +0000 Received: by mail-lf0-f54.google.com with SMTP id h129so116217126lfh.1 for <>; Mon, 04 Jul 2016 05:19:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=xNUFVCkzn1/B6vibiwOTzlMPTjCulRhoAA9bqY6aT1U=; b=gPKX2kspLWSqMQBatxPMBxfMgDvw8wUOD3a3V2tf+tcPBflNXkhy6Oez0WaBGWEgiO UIAGTToQOUEBVIa5uub45si6coYucMXqJVTXek6cMhMxLHtqTn0iTfawOnympFLpDNQL gprYnBLdEpgiaRhOCuFPI94x7GYPnWSUiY/cSVK2cUUxP1TJ1Jf+pSPL9ZFK8gRhoz5j 0jtyAt/Sj2id83qyJRoRbAxu0mZu32JyBP7+ILXAtvx7zGIIH9262TKsNXZ1TTAnwEKs tONSWYa0UF/pjAI054VNd37VsXLQat7Ew/ST5N6azNy7HMBTu8G0qY6b8LlAbJfbhnp1 AOeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=xNUFVCkzn1/B6vibiwOTzlMPTjCulRhoAA9bqY6aT1U=; b=NuPQpiFLi2oQvvULz7UOtBSx2AT5v9xAComFG9jxlFo1/sl2XGri6FDiRUzekKguwi 9oAcfum9BDRqdLiPdqNRbZYXas7mt35oo0OlXdRWNOwHpnkRpZ1movxSelrb6YySDD0a bn1na/h7Iy7oPxCV4+j48bjMoZFajhfvENXQp2xck1PasPdZmh4fngHbYoPyAwBrAx4N iNyuuxc1YB+07ernEUOQoyUcSOGJps40uKS+HeR+Oo4p9fwq0nkui72hWb32eA4cadt+ g5rxSXpXEmhammeUtjyroNnYpx9bvY8ckRvGwuQQOOp6MY55BTr2mpQuEIvCumJepQIM ek4Q== X-Gm-Message-State: ALyK8tJBeKHAad8FCiEgenLOqpK24G3XYSMl1oCEgHD7Cs2xOZF1NyhQS2xPhQKh+LbOJ5rJMzVb61KxZD0Y2w== X-Received: by 10.25.142.143 with SMTP id q137mr2295223lfd.53.1467634768589; Mon, 04 Jul 2016 05:19:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.154.76 with HTTP; Mon, 4 Jul 2016 05:19:08 -0700 (PDT) In-Reply-To: <29847.1467231631@sss.pgh.pa.us> References: <29847.1467231631@sss.pgh.pa.us> From: devel.brain99@xoxy.net Date: Mon, 4 Jul 2016 14:19:08 +0200 Message-ID: Subject: Re: Random slow queries To: pgsql-performance@postgresql.org Content-Type: text/plain; charset=UTF-8 X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:ff10:c5:506:225:90ff:feab:5c2e (deferred) X-Pg-Spam-Score: -1.0 (-) 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 On 29 June 2016 at 22:20, Tom Lane wrote: > Don't know if it would be practical for you at all, but if you could > attach to a process that's stuck like this with a debugger and get a stack > trace, that would probably be very informative. It seems I have found the cause of my issues: my antivirus software. When I tried to debug a stuck process, the currently executing code was in some DLL without debugging information etc. When checking where the DLL came from, it appeared to be from the security software I had installed. I had been meaning to change because I have had some performance issues in the past (nowhere near as bad as this issue though!) but hadn't yet gotten around to it. After switching this weekend, the issue went away completely. Even though I had previously noticed some performance issues with my antivirus, I must say this still is a very weird failure mode - especially as it still occurred if I disabled all realtime protection (one of the first things I tried, even if not mentioned in my earlier emails). Thanks for the time spent trying to help! Best regards, Roel -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance