Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dzL1Y-0001JA-08 for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Oct 2017 11:06:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dzL1X-0005kF-G5 for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Oct 2017 11:06:03 +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) (envelope-from ) id 1dzKzx-0002n8-6r for pgsql-hackers@postgresql.org; Tue, 03 Oct 2017 11:04:25 +0000 Received: from mout.gmx.net ([212.227.17.22]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dzKzo-0003la-Ux for pgsql-hackers@postgresql.org; Tue, 03 Oct 2017 11:04:24 +0000 Received: from moll ([80.187.99.184]) by mail.gmx.com (mrgmx103 [212.227.17.174]) with ESMTPSA (Nemesis) id 0ML6XF-1dz40m0xCj-000OcI; Tue, 03 Oct 2017 13:04:09 +0200 From: Andreas Seltenreich To: Michael Paquier Cc: Tom Lane , Andres Freund , PostgreSQL mailing lists , Alvaro Herrera , Thomas Munro , Robert Haas Subject: Re: [sqlsmith] stuck spinlock in pg_stat_get_wal_receiver after OOM In-Reply-To: (Michael Paquier's message of "Tue, 3 Oct 2017 09:54:36 +0900") References: <87h8vhtgj2.fsf@ansel.ydns.eu> <20171002210805.x4lxxmarluen6rfg@alap3.anarazel.de> <459.1506979825@sss.pgh.pa.us> <20171002213215.4e3iwt7oh5wdjqm2@alap3.anarazel.de> <665.1506980082@sss.pgh.pa.us> <1409.1506981260@sss.pgh.pa.us> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) X-PGP-Key: 4096R/803D1FFF 2015-02-04 Key fingerprint = 4758 81DC 8539 494D 29B4 692D F587 0601 803D 1FFF X-Now-Playing: Orient Orange - Hello Everything - Squarepusher Date: Tue, 03 Oct 2017 13:04:04 +0200 Message-ID: <87wp4csdaz.fsf@ansel.ydns.eu> MIME-Version: 1.0 Content-Type: text/plain X-Provags-ID: V03:K0:HF7AcoTVRBbBjkkifH4CYQrM31rqwILng0ixqOyC/KxLSsvMTwQ kw0r0u8jRfpVkfM602Kt+nLd9Q4aergxRPkUJU5RS/jPW8mgU1wvJN+xLzqwkiOgT4uOSJz X8CRd8cDh0MEiwZcaxl7ZwrHssnlLrd3heF+vnUNezHZ/eVARqfsMzMCaTVNzdutxm2990R 1/19FFawndaAUbeFiCxTw== X-UI-Out-Filterresults: notjunk:1;V01:K0:fMCYFBuySn0=:sP8m22eWPe35iMXNu2xE9b FwHUl4lI6AWyC3RknfOyPQAwJ6rlXbivFPSjF3a0MCFNZs64aUrrj1qsLiQxiuXViEj8av649 qszNexbP13mq2dTG1pZt19pGyxxf4X9LOpBJN2bA5oXGA8ceF3YNsDi/QrfyNuFqgfE7I715D ptcsIfVutG/CQVImhaiV3EHACl3DB5oAwkaE2VmKDy3qx9QOEPNGwuAFR7eJ/BPHGmQ9Lxccm k8wgFd2L4G5ha67jjDCHY3hKRan7bCl7hn302XlZsLTYmBk0u54xzsqeBtxcB7i3Jw7zwuyZE 4zbUh5OHFo5Zr1oV6yMkLNb4kAq/R5rLxYJ5QKq478kp4tgUpTI5thsolu29SxHdiLeOaJpH1 a7hLnvKqLaTee5H7dC4jZ1TFjTNk1Ta0jExog3ARHOgWm/QrxJ6xYD+M6ILjR37ipwdbt+evM kihtbTVJHNgIN+fouqjQp1kYjPQCg6hOem8e0ozfxKxrkvmAk6HaFMbky5gscPgVSrf2t5qkK LI3F0A79fpTcPNPqWPn8/YtBjTNAAGCGEgi65goUle8BrqsuWdiDR5yVD5pVYpLv3RTtTNYf9 yJZOITXYAWeAZMn2zHwDueCMpxbjSiClcpgrSyU4deho4i43+2l7SLbNn1n7FuPiuhRQhgH6r FFwmtYe2WqbsF2FA4gbqka24ka7w+sjlLrRVeAoCcN/nqavpfMUgw4kK4LKW0os6kGnoaJDZt Z2bwsA5UbEub9yXZD1o1/eEaLlr8SR12YEhMs0qEN8B3lVMWNB2/4iIQ2vwuE2geuqsDJf0mj feQvM/mWiHmLIWLX88CxgMl/wDcPa3frm9LZbGkxD4OHAHsUJ8= List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Michael Paquier writes: > I am attaching a patch that addresses the bugs for the spin lock sections. > [2. text/x-diff; walreceiver-spin-calls.patch] I haven't seen a spinlock PANIC since testing with the patch applied. They occured five times with the same amount of testing done earlier. regards, Andreas -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers