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 1iWtoq-0001ly-QY for pgsql-bugs@arkaria.postgresql.org; Tue, 19 Nov 2019 03:04:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iWtop-0007ZT-Gm for pgsql-bugs@arkaria.postgresql.org; Tue, 19 Nov 2019 03:04: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_SHA1:256) (Exim 4.89) (envelope-from ) id 1iWton-0007ZM-UR for pgsql-bugs@lists.postgresql.org; Tue, 19 Nov 2019 03:04:43 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iWtoj-0006Hk-N6 for pgsql-bugs@lists.postgresql.org; Tue, 19 Nov 2019 03:04:41 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 7975C69C; Mon, 18 Nov 2019 22:04:34 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 18 Nov 2019 22:04:34 -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=IZ1wi8zFW15LwuHVLR4hVp9vSH7 YJDVzr5tFlMuE3J8=; b=hgoTaYgshWjES8dnwFymTS79nHBxoVe8vylv0dMmWd8 zxPtaW+r2exH/ey9r5Pe8zzNrz75zImTvZdSiCDl1frp/AfLUwqew4D7yqVCHX9e FHUsFCpj+ZHU7dml0lXXm6Q3Pjr3fHqLA9wKvCQPzzn9CC5hiAmVjg4Jv2JR9aqX m7c7hvwaG3Elupb6dgbVRwvSvWZjlS6QHEagPL7NtQfunkVXemR3v+TjuhJkT0Bh e++S3qTzkkBp2VZgIlann9h5ARNssBmblsy74nQ3AH4rM1pYeemEy5C2va4n5qb2 Ur3d6ab9/AFIsa04jNycaN+GRKq97AbHDIXFZijBUbg== 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=IZ1wi8 zFW15LwuHVLR4hVp9vSH7YJDVzr5tFlMuE3J8=; b=cD4rHeYw/iq85HmPYv3jKY qYgsSDO+u0vKbervs5OpQ7iXmjf9rAhX2oimRufYTcSjAcDbGqKXtNti+tkm257T DaPCMERrwR3dcz5s2MA2g6VYXU8CzXjLHYWoMCFd7q00XiddnbD74nKQclaBAvrY mXdK5QgOfeu4oAAqkMrRK+ydjxezFzOtetHye2FRwN2kupMGor+QL2YZkRh/TrG6 T7swlI3XEoCsRaxK2N/d/MzdphmPsod5b7tk6C/hNAus887Y8C5Mht9fkkBFfsO/ 2eRN+Jwit5J0YZApRSwZx+6OtIwWKB+4thHxZE9j8CwZBY+dScKOB5yjTGOC3Z8w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudegjedgheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlfeehmdenucfjughrpeffhffvuffkfhggtggujgesghdtreertddt 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 86825306005B; Mon, 18 Nov 2019 22:04:32 -0500 (EST) Date: Tue, 19 Nov 2019 12:04:28 +0900 From: Michael Paquier To: Adam Scott Cc: Tomas Vondra , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query Message-ID: <20191119030428.GD1614@paquier.xyz> References: <16122-eb35bc248c806c15@postgresql.org> <20191118120312.cblcswef6vuqbijq@development> <20191119014827.GC1614@paquier.xyz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UfEAyuTBtIjiZzX6" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --UfEAyuTBtIjiZzX6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Nov 18, 2019 at 06:22:11PM -0800, Adam Scott wrote: > Maybe a clue to the issue, why does a numrange need to be detoasted since > that is for large strings? I looked at the code a bit but could not really figure out what could go wrong. Then I switched my strategy and bisected for the first commit leading to the failure, and this is pointing me to the integration of stdbool.h for my environment (Debian SID with kernel at 5.3): commit: 9a95a77d9d5d3003d2d67121f2731b6e5fc37336 author: Peter Eisentraut date: Thu, 22 Mar 2018 20:42:25 -0400 Use stdbool.h if suitable Using the standard bool type provided by C allows some recent compilers and debuggers to give better diagnostics. Also, some extension code and third-party headers are increasingly pulling in stdbool.h, so it's probably saner if everyone uses the same definition. I have also checked that manually and I am getting a match. And the thing is that this commit did not make it through 10... -- Michael --UfEAyuTBtIjiZzX6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl3TW7wACgkQnvQgOdby QH2Z5Q/+JjX+uVGUU4WGW0GXoAVr2k9S7JOjZPwlE+dydBJ1ZnKIVYNknev2qLyo 3T36e7Z6fWj+4LKZPTslKGktLUUdv7BeNxaykFjEIXqf3AwEtfAjRWGxY95VtjL3 m/LKapakP5IMQYDjSkZJ0D8CXfF9bTm1tJq/iwaTQVItUUKQSfH18FQddsiq9O+r N35gfr8TVv2yyux5i3e1f6r0x03MM66hDA3pJV7+SP88Z5Oi1e5rOmTQRYJOlONR PTF0CL+YToDgGuPBi26oefNkVrVo8BQJV2GQ90DbtVLDaYeFPYMIkPZJtwYemG3X ICd9QjnThVzDmeUCOz/2je9VDZUohpo8NQeqx4GSG+KEdHNuIz6G7rBNChp4gaxK vKq1xyx4gT/89avy4SuJRSSvSdSMqFqgVyy3AkI00u8zdDy2ijHy0VeGdBXtQAzc fWrSxu4W6l4IwtxXRqLYOQ3ZqKDZyCeFDvg9q5qiVA4wwYIYDZQ/VPVKiewZSiqK XgXe2vysj1ErpXcnPe9kWeMSY9tKaTxP31levf4dJFHfYDiiRu469vsXlt+acqe6 /EhpQy23JZSxhKAWtyqN0O5Un51qRfaeHHB2mTNLz8CarMhXWq7S2MsaHakI1WM1 /6AMvMv0vTVO5Ns8KU7cZWWw1DHr/nNGGgr/IJspOIiQcBXMyuU= =4n9p -----END PGP SIGNATURE----- --UfEAyuTBtIjiZzX6--