Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q8a4O-0007LZ-VF for pgsql-bugs@arkaria.postgresql.org; Mon, 12 Jun 2023 05:26:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q8a3P-0002SN-JM for pgsql-bugs@arkaria.postgresql.org; Mon, 12 Jun 2023 05:25:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q8a3O-0002Qb-Q6 for pgsql-bugs@lists.postgresql.org; Mon, 12 Jun 2023 05:25:23 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q8a3M-001jEl-5R for pgsql-bugs@lists.postgresql.org; Mon, 12 Jun 2023 05:25:21 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id DDFBB3200902; Mon, 12 Jun 2023 01:25:18 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Mon, 12 Jun 2023 01:25:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1686547518; x=1686633918; bh=u9 KtCjPSdj9UCEer3Vluwj7tpCndGzB2LRllSeF7o50=; b=VOcQXQEdkGOUwM6zZ9 yX10XeiGJMpp1IJJ8Kb8mPzzvegZTTaOZHSsc9AniGPvru/KePhLoPSWC6nkxzaR ApRzRX8Su7ezVy6/nko8Fzs8F2DeCrMaLNNmvwEXPTYOsyQiG98/A6ha0RllMkjW xpLLiKzghRiuviTs1g6fOPuvXrss05A5hUbMdzFl1i5Nwe4XV0Awk5QryrptVU9M nP2RNRjSpwEN9AgMdsJuNUvEWTERf1PYFoN73NX0kLw0pp22or2yzChLSIBbhb3Y h6aXaJR5OLJBxIaVP7Dz5P8Geyy6A8PkNnRdEogDTtjKx75vh9+PMWuzU79GItxQ rMLA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1686547518; x=1686633918; bh=u9KtCjPSdj9UC Eer3Vluwj7tpCndGzB2LRllSeF7o50=; b=na+3t6YlXmh8lIDy7WS9bD3yM1fvw cRBbnFFy3dBgbB5LHEhMfdSnE9Zqmc26M54Ooan1q23scndkTdw8qKDiqQhrfzy2 jVFFFcAdFxWsP3g1+f2Dap3P1VUH8J0cCj0DPX83XluGfSRqqPpXwNUvGbbS7037 s2uc0IsOtQHSiP5RrMzFsBvw8zeLWuxE/o4naRJKloMg+G2Tivi80bhbWLEQPNJc ui54Y7FVkP00LMUXAmkngcMur44GG36QQ85AUzQ3B513oDH5xYUXqU/bVMNpp/As atzUhDeAm+kuOY9os+nIIJXdaY+nGFCH6dRRED5LE9zSBohBacj5sfgDQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgedugedgheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeg geegfffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiih ii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 12 Jun 2023 01:25:15 -0400 (EDT) Date: Mon, 12 Jun 2023 14:25:12 +0900 From: Michael Paquier To: Nikolay Shaplov Cc: pgsql-bugs@lists.postgresql.org, Kyotaro Horiguchi Subject: Re: BUG #17962: postgresql 11 hangs on poly_contain with specific data Message-ID: References: <17962-4f00b6f26724858d@postgresql.org> <20230606.140749.1678060452808896223.horikyota.ntt@gmail.com> <20230606.141736.939081296219135931.horikyota.ntt@gmail.com> <31814440.0auUPBzOZ3@thinkpad-pgpro> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="5LmBJBnRnjRbZya6" Content-Disposition: inline In-Reply-To: <31814440.0auUPBzOZ3@thinkpad-pgpro> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --5LmBJBnRnjRbZya6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jun 06, 2023 at 01:39:06PM +0300, Nikolay Shaplov wrote: > Hope somebody will apply the fix to the proper branch :-) Is that a side effect of 6bf0bc8 and 764a554? Hmm, I am not sure to see how this refactoring is influencing the result here. Anyway, I am not really convinced that we need to do anything here, either, knowing that v12 is able to fail early without relying on check_stack_depth(), and that v11 will be EOL'd in a couple of months. -- Michael --5LmBJBnRnjRbZya6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmSGrDgACgkQnvQgOdby QH1hYw/+IAzBoYu070KQU89Aqeu19+8rvCqNMsqAevUUjM/05cWrV6wwyXmqO6Yc sAf30H0q0Vbn0ouQKkUotncnjPJJKDCyEjJcCX5HdsjD12OZ+T4rT0yOC9Av3Uvb YMpzSgx8mmZiPYuX1xuLrpgHqdqYmaKyLJ5CJ2ZWlIdJL30gGAWWiZ0aaQKQbHhy BmX5BrkxCZTDqmIZgX7Lp+kUt3y8jqBB+Xyf4K52XCcg6KM0VAKU91nA9xmFMahs JikEAtjSCB5anHBRhxVq9WfUNzUwyveoFlJ51gGVKPqMxlY183cEf09QrCNOaKk9 4gRkFLq8I5Tsy8GN8fxgE4MKS26ne3UARw2A4JLW/PIN+/+0pg4p+TBOHe3bK0TJ Qzeeyym1OOcZPKlNUxdT6ABNKCbMZq0QReDZHDIrHc+b3OtYSGO5TI480Ico+78I Xd7zFIjZx87YiWdu7xKjItOiP73YzP3CSl+vKFmhdquus9CAXNuNn+IVDyEtyaPQ HnpT6A6FUqOJrQD8jhysTGquKgztzm6nCBC9wBFPBxV7irHZWYQKiv5a/xARrbsw KXpbXmcjTqBuT/R9EWXMFESjHq9108qrJcBSf7hpNzMdTAiR28Te7k6HKRHfRUym +b/e6hgtK8HNyjjv6TZqljHoeiMSpto9KLZqBxq8e6QEGsR1WpY= =d+hV -----END PGP SIGNATURE----- --5LmBJBnRnjRbZya6--