Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rXAKN-0096ZL-Gv for pgsql-bugs@arkaria.postgresql.org; Tue, 06 Feb 2024 01:32:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rXAKK-00H0us-Vv for pgsql-bugs@arkaria.postgresql.org; Tue, 06 Feb 2024 01:32:44 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rXAKK-00H0uj-Ni for pgsql-bugs@lists.postgresql.org; Tue, 06 Feb 2024 01:32:44 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rXAKH-005HHo-Gl for pgsql-bugs@lists.postgresql.org; Tue, 06 Feb 2024 01:32:43 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 7CE645C00B7; Mon, 5 Feb 2024 20:32:40 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Mon, 05 Feb 2024 20:32:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1707183160; x=1707269560; bh=Fijt0h15hR aJBxVOFgDPyjm/ss8Izf/Qy/kzSVQK11s=; b=maip3I3yolXV2JW5aYE7lzkJxC vbJHkhAtHq2CKHgQnOkjK4NJSTpMdaHLxATbRgNke9XCkYfsUuazXILfk9e7kTa5 UK6FJm1++6C+p+Yzxv5Fads+/1IiJ9NvHwvLuM7xjb6rCrgmiKi8SOVtGnc4Zf0V nqAuVOMuNYV49oD8bGWn7VKObo7oSdmBscKcZvJK2CTmJY2mGccgWsUfOb/gq6FP yU8jzjwl72Mu9ZRqyyxm3WRSDZYRd8F95BBrrll1SUr9bJBdxOgu+UvvaHAdTFvh EG8iN+HKsdeeAsBDPfLmnMlPv6DM1L9ghrJRqDWC+OY7uH9VLF2pywAGkBTQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1707183160; x=1707269560; bh=Fijt0h15hRaJBxVOFgDPyjm/ss8I zf/Qy/kzSVQK11s=; b=dmbMDVs+U2Pc+v0EkrXFdQheExMk7Df+Cn3uaOdNaiXK PsPpPgHXhMV9i4N1IZM1nTLKyckF0xUEBX/vCd8NnhiSvgeSpDAJO7gXxqS0QiQ4 Pmy8B32ZpbyQaMVa+10UpUhLmHXKEO132Jo/oyQFuR+nrnNO/4hIXeqfVcVMjNvp iNiICQ5+uIJLEjfzVm6Gx/gli1KW/qcLW4cp+jOR2WcouNOu921mQ/IDUXTNWLJM fL9kVseBCZKHR7llwA7wm4gYqov0CINudQnIOl//+vO8GMYuu/OEdIWve218of1u PdNUyobGKLbRqC3YcgbcxzuLPdR2WzMuhIx0UjFDqQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrfedvvddgfeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdlfeehmdenucfjughrpeffhf fvuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhu ihgvrhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucggtffrrghtthgvrh hnpeffudeffeelgffhkedukeekvedvudfgieetkeekudelfeevhffhffdtudffieeutden ucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdr giihii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 5 Feb 2024 20:32:39 -0500 (EST) Date: Tue, 6 Feb 2024 10:32:25 +0900 From: Michael Paquier To: sujeet.cha@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18333: Postgres is crashing if we have special character in the query Message-ID: References: <18333-8bd5cc3619b15618@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yGU20SA1LMiWT0Y9" Content-Disposition: inline In-Reply-To: <18333-8bd5cc3619b15618@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --yGU20SA1LMiWT0Y9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 05, 2024 at 10:30:33AM +0000, PG Bug reporting form wrote: > I have installed Postgres-14.10 and when executing the below query, the > postgres crashes. but the same query work well with PostgreSQL-14-9. > I have a crash dump, but not sure, how can I attach it here. >=20 > 2024-02-05 06:08:53.936 GMT [1680576] LOG: server process (PID 2627861) = was > terminated by signal 11: Segmentation fault > 2024-02-05 06:08:53.936 GMT [1680576] DETAIL: Failed process was running: > SELECT DISTINCT badsql.id_code,badsql.id_nr FROM badsql LEFT OUTER JOIN > newsql on badsql.id_nr =3D newsql.id_nr and badsql.vk_ek%2=3Dnewsql.ku_v= k_ek; It is going to be hard to say what's wrong without more details, like a backtrace, or even better a self-contained SQL sequence that makes a problem reproducible. 14.11 is planned for this week, so you may want to give it a try and double-check if your problem is going away: https://www.postgresql.org/developer/roadmap/ -- Michael --yGU20SA1LMiWT0Y9 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmXBjCkACgkQnvQgOdby QH0eSg//QfB9gTUsjO5huHUxjxJvo3WziQXNU26Kj9W9ObDyyjkRjqXT3OKnQOKR 7vdw5ru2/khqby+Ch+idY6T6yM8Aj7CXSoNfeClqADPLVpCeTTwBmsu6Q1OdarZv cij5CWQQbjBso4ZN1baH2CXulxFZT0Oidv5P5UmmgyI4Q3vYYBx6+2SvpQOtl7wb xR28WaBcM6N97wZO8rKaCxcIHaauC3+PyXIzdAiZv8c0BUonDMYPQcTxWKb7EB0B JQSMLkTsdnY6rK0ZMghYXeXg00TyTj47F2fassfx6ZDs5HeN96ERGncDc4wWDZB8 8o6vebDlDyNxd1aUeVVjAMe5/I6BcYmx/8Jbw6kH9VKo1bRvXXI1lYH/uov/Lum5 l+RfrbFdh4JSF4N4JsowM/fGN5GDJcU3Jd8cHZ0OtLu1FdlNJXKehZhZvQSVcybh r5qHajA9PDLjNo90/Pf12wT8TwcK/y4/NvE7op+V4brOJJZzWSa6SRuaS6L+hfbY pa+Srjx/HtyY3OsQhn+QLLIH3dBhAYZuvKGSOixG/7q7tofGJVgkkp+H/8NXiZZI N8YRDKBgrjPHNI89fVmmrIxG7sl/fWhG65BSnIXsY9iccveNg+SIzVW48gYF82NF wA3kvigzWHP2LWLP68tRgeSqCWDlJiWL9KmfaAwhdbLJiSjBdbY= =AGwY -----END PGP SIGNATURE----- --yGU20SA1LMiWT0Y9--