Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fy2IZ-00004v-2i for pgsql-bugs@arkaria.postgresql.org; Thu, 06 Sep 2018 21:58:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fy2IV-0002ZJ-W2 for pgsql-bugs@arkaria.postgresql.org; Thu, 06 Sep 2018 21:58:43 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fy2IV-0002ZC-36 for pgsql-bugs@lists.postgresql.org; Thu, 06 Sep 2018 21:58:43 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fy2IS-0005Ev-71 for pgsql-bugs@lists.postgresql.org; Thu, 06 Sep 2018 21:58:41 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 86A3321F0A; Thu, 6 Sep 2018 17:58:39 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 06 Sep 2018 17:58:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=h6GGMKJIJvjCgdeCM5hhz7PHWXc13D2e6lVyEqTwrv0=; b=0jfzzYWD GmoRera2iNB9S3q88A/E/n8xsvxcyVnD7f+trEzNLdwuN/axfg2iUlhqqme4kEy5 DhbATw+zyq7EDNWbDZSCrNOQtUan2QPVxdqtPBJ2im2qmeu21vUxmwEOik/x5HrZ DX1JANjDV/+oYZ4cZ1282O8ibQVxRX0CPv/LVmhcEkT9zvcDtqC06IiIhYQO4sos d0hNPmB250FFeuzxZwrXc6Uvj9b1tYA/RkpoPP6eumGdb0YJbRnBoNhHMYcg+ggY JTCKIhOKlT/1qVnUfCqsgVr9+du5asZkvJSV2jkYRvuIHIo41NoTtAYrx9yigH2m SHDuKPw4WnQntw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=h6GGMKJIJvjCgdeCM5hhz7PHWXc13 D2e6lVyEqTwrv0=; b=Cbw1H1wyF2M4kO8/LaW5LPPDbVxSQAuROmuZvQCHvy13G dm50na3jrHnEfePk90R4rZE13V2PCcbbwQsGCNfUZE1WhNiPfW8yRDodzCj83KGX pX/TPYACCh1tVsrI88Jkb9IIxBXp5Rn/Yz0kT0UEjzTxWVmy9MnezB72UmZH5wYe Yd+mu1VgMbdmsh80PuJxOsO7LY86bLsFHioE2BwGD1BPW/lnN6nbv49Uc+v0l6X6 0OxF5lh5ik7fK39uf2lymUUf0f0wGPb/8ldPMr4FBdEY/NowTdcvUtBlIuTyB0RT 7Xvk1Cw54w4PvcpVC9e6D3LBDWwd/YCxbcCMN7s2w== X-ME-Proxy: X-ME-Sender: Received: from paquier.xyz (unknown [50.233.106.125]) by mail.messagingengine.com (Postfix) with ESMTPA id 73E80E447F; Thu, 6 Sep 2018 17:58:38 -0400 (EDT) Date: Thu, 6 Sep 2018 14:58:36 -0700 From: Michael Paquier To: code@jeremyevans.net, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15367: Crash in pg_fe_scram_free when using foreign tables Message-ID: <20180906215836.GP2726@paquier.xyz> References: <153626613985.23143.4743626885618266803@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="58yjuNbz5lCTNNJH" Content-Disposition: inline In-Reply-To: <153626613985.23143.4743626885618266803@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --58yjuNbz5lCTNNJH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Sep 06, 2018 at 08:35:39PM +0000, PG Bug reporting form wrote: > If necessary I can build a debug version of PostgreSQL and try using that in > production so I can get a better backtrace if it crashes again. However, > considering that the crash is rare in my environment, it's unlikely I will > be able to produce a better backtrace for the error quickly. That would be nice. From what I can see this would be a race condition, which is not obvious by looking at the code. Testing with a two-node deployment where the first node has a foreign table which connects to a second node, using SCRAM authentication, holding the physical table, then doing many foreign scans across many clients don't show any problem. Did libpq complain at some point in the session where the crash happened about any error? -- Michael --58yjuNbz5lCTNNJH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAluRowwACgkQnvQgOdby QH1s8w//Qjtmh5wzP3dZcHWZN0givZkYnQOg0Tt6plf2PGm8BicYCsr2bDMvlCFB JFHnAjjR+pmwqPZ9vJ4hRKFxfnSrYoGddnZ3L2px0QA7xFG9hlMraQgSgMHqEU3j kIIpRSHvZup0sdzuMPAO32ckDB8IZ/FIoYlqVfwYWSiB925csex8jf+0k9LnZ22x Azs2LyA8Z3Ab+HmE9hUmduahrHJ6cfzRFVTFQcZq6mX0jVg2eNpdwjzYsYo+9+Vh FgANBI18vAT8Ay6hA4umhKr0lkKLW1V8+Ouf+q0xjaKGJonZtFhObvhomv9VPc42 A5jkV1RG3en78eq5YiAJxLqVYnhSMNPUKqAYpg9j0HdCiHOsI2gJwwbsIvinueG+ J6BJKmmUhFxeWy8S4tTOEp+TFgn6uYA7u9ZLDBuLSUKkIQ7HMzGM1QCgenr+xINF uShh5dVJD5kEo1xyizB3cV4Lcdlct60AlxkSBbyjZhSDSdgEw/DJZHdWYJORxXHC kD5UYQV0Qx7RgQPwOmH9p54rfYP1Rzrxo5WvseHsypUkhToffC1s6VrCLJaMS4g8 yBksuOFHJEFtxuQt2BEQ+zHU3rqTD/0r1xNCSVwevNf2/pX4Ru7nw5UcsuS3Glm5 YYgbJNrz9Fs/mTIa6P2gWu5IvweAY8tjsZlvVayPXqrSX/y0OxE= =wiM9 -----END PGP SIGNATURE----- --58yjuNbz5lCTNNJH--