Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSXhb-00030P-3B for pgsql-bugs@arkaria.postgresql.org; Thu, 07 Nov 2019 02:39:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iSXhZ-0007Rz-Rx for pgsql-bugs@arkaria.postgresql.org; Thu, 07 Nov 2019 02:39:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSXeV-0005AG-21 for pgsql-bugs@lists.postgresql.org; Thu, 07 Nov 2019 02:36:03 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iSXeO-0005hs-Eq for pgsql-bugs@lists.postgresql.org; Thu, 07 Nov 2019 02:36:01 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id D71FD21540; Wed, 6 Nov 2019 21:35:55 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 06 Nov 2019 21:35:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=V5bz5P1Dv6s8V3eAM3b+NO9or8H /fU7HKdTFaqp20iU=; b=ZZPcsVopqJDRUEDqLv70QcuK8pxP0lm896cuVg1SxEB FMDgxfYYmHPagIdk15u4fmEcWxrTe5YnYZUE12DTALy2aZ2Zy2kPHtd9LRiNr2Bh nTflhLVuHy4Jdj5hsML7VgKEMoZCVELnvWmKEwaGfgKMDUDGvrZtLLgfhhTyAxq0 QXlKbE9CCYcu8LCAiCeZED6pWZWy25x+LbpH53Ovkj7MPJb8umpc/FBscMPgBb0i 94XKc6kaAMypl2iN3QeJ0+0DuXVNsVGaNqaS/S+RKfRchyEMG6RlaWF6AfzdTzGX n3Ebw+tHWGJnmEXsGSQf5naWqaAPc4JZchVAZrDtBTQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=V5bz5P 1Dv6s8V3eAM3b+NO9or8H/fU7HKdTFaqp20iU=; b=IUy0ztOK6IYyTLu683gHm3 9A8QoFFaVxBv4ut7CyHYxESoVHWuO1qVleSp+VRjmGaUa06h2IomoCdOAQFrFS8W DPOC/XI2HzolyXApMqt4yhsE1Ox6lTLzsyuqvG9D75EFrHgUD+DjPVDDf08mvfhG DmLO16KS/MpJmegixHpom/mKaUWq+XZVUb8S7bH/HvQQgDjTxokqhjMnjuRCF5T/ XWhazUqdcW5t3G0yRb2x2U2cFjuf6mZD7zYWcvfwHZLVkKrYe3XXqZZc/fzsz3lP ktXrI7bEKzTnPxG0kSzwfuDRVno6SEkq9waLw1ZiSpSz1I9Djdr7aHTA44VncLXg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddukedggeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucfkphepudduuddruddtvddrudektddrudekheenucfrrghr rghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihiienucevlh hushhtvghrufhiiigvpedt X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id 5D32D8005B; Wed, 6 Nov 2019 21:35:54 -0500 (EST) Date: Thu, 7 Nov 2019 11:35:51 +0900 From: Michael Paquier To: Mircea Pirv Cc: Tom Lane , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16094: Database entering recovery mode Message-ID: <20191107023551.GG1768@paquier.xyz> References: <16094-8fb7061e5370fb00@postgresql.org> <6649.1572879825@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ISKrrfpKsPiF35CV" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --ISKrrfpKsPiF35CV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Nov 06, 2019 at 03:37:31PM +0200, Mircea Pirv wrote: > #2 WaitEventSetWait (set=0x55bc137a5948, timeout= Cannot access memory at address 0x7ffee2d44ae0>, occurred_events= reading variable: Cannot access memory at address 0x7ffee2d44ad8>, > nevents= 0x7ffee2d44afc>, wait_event_info=) at > ./build/../src/backend/storage/ipc/latch.c:1032 > rc = > returned_events = 0 > start_time = memory at address 0x7ffee2d44b00)> > cur_time = at address 0x7ffee2d44b10)> > cur_timeout = memory at address 0x7ffee2d44ae8)> > Backtrace stopped: Cannot access memory at address 0x7ffee2d44b78 Is this the only part of the stack you can get? WaitEventSetWait() gets called in three places, which are be-secure.c, syslogger.c and condition_variable.c. Could it be possible to see more of the actual callers here? -- Michael --ISKrrfpKsPiF35CV Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl3DgwcACgkQnvQgOdby QH1IDhAAok2LmjAOA4M1D2+i3/eRzoZyaqevNFJacsrTqZ4B9UZUyTL24IH0TQ7d stmNzWNWPXcURABMy2M9M3OkW7GqHZIhIbEghDFjvoO//NIiJeS+XHgqFA/5kQdp B8Xr0uLtywvMpyPBXuhXBSkAhY4v5H6wXVBp0sVhjiPsJ2JHUJibX/MgVYDjWPk3 Q1gedn35Z43MnyhpgMfjAlkESoNrmHsgGmrJ9xAF1lAaHEVwQxKrXJ+QmW9TUss+ OOXsWPuRV5eOVEQWGVMH7rc3ENHHQNfxYFr9ElESW2kp+gHFEwIySIPw+xeE4rXi PGMu9eH5xKjf+2L1I8ZNXAH7MlHK/bmdVlpE2nEybDJS7DeINFs3eNk0zCII/QZD hv5y1OVjHpUW96GaCv+mw1tXNEzSqHjK4WCevZrZp7UAqEI5FLWQzqdGf0LDQw4M fvSruA1JUsvHXCPOnS1KcfTQGMS5IHmgSJXX7HuVgUaBjuDhEay+WLdQtdWLxvBa Q7iyxdxyq2S1WqTaYZo2DGctJRcmP9ZBLLrb7GnPLd8JYNOYk7qllc8vbC0lDAga zRi6GDpBVBeMIqETlzfsPAMFXQFKiXuqOS/BPzQaDkRW42zTlKCs8mj2MFIViY2M t3DiSorH5EWvELfBTVYd9YtIbubZDSJZ2c0O59P1Kmpupd96YiE= =UJWq -----END PGP SIGNATURE----- --ISKrrfpKsPiF35CV--