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.96) (envelope-from ) id 1wExe4-004cJv-1J for pgsql-committers@arkaria.postgresql.org; Mon, 20 Apr 2026 23:03:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wExe2-004n6e-1K for pgsql-committers@arkaria.postgresql.org; Mon, 20 Apr 2026 23:03:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wExe1-004n6W-1b for pgsql-committers@lists.postgresql.org; Mon, 20 Apr 2026 23:03:10 +0000 Received: from fout-b2-smtp.messagingengine.com ([202.12.124.145]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wExdx-00000002CfQ-37AS for pgsql-committers@lists.postgresql.org; Mon, 20 Apr 2026 23:03:09 +0000 Received: from phl-compute-03.internal (phl-compute-03.internal [10.202.2.43]) by mailfout.stl.internal (Postfix) with ESMTP id 1EAF51D001BA; Mon, 20 Apr 2026 19:03:02 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-03.internal (MEProxy); Mon, 20 Apr 2026 19:03:02 -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:subject :subject:to:to; s=fm2; t=1776726181; x=1776812581; bh=v5JdgwL9BE 67862lo8aT9Atwhvkt0UAO4ZNybHkbNaI=; b=Y21k4968tWDTR6vmMbhe0Wn9bg 1iiXlxsdEEpgivuFrNgG+ATwPvfD0lr4xfXrX5Cambv2vzgirn76ApXjQGsPeN1U LlRoH3xk6UD+MeQZXwP4sDRpkTE/SaIs4Dwwj7eXAg1YifRKIiLZqajNWbwvUQv4 lNSQCiWaPtu76+fQvVh0udCdA/TmNuSqH8RzZ1fKigjSZoxSzHfHFNtTuPo+r4C8 1XJXbKZH3VD5dS+lRX8/Axou54Hc2jAFK9jddJDgFLpviavm4iVPY9VQJ0e/AwIS iTf0XkEdaPKIIpzpAacTzhTU9xQBPPVeqka91B8/+hcgx/vwf2tbZ2Xbrslw== 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:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1776726181; x=1776812581; bh=v5JdgwL9BE67862lo8aT9Atwhvkt0UAO4ZN ybHkbNaI=; b=l7i13fYUE242vP5uFymSKHw7uZynfHaDXhDZukuh7MuXNBSie+/ +Qy4ZgVcSflBd2MdumHmDpAiLUfcITWX2DCTYF4ANplYr+vSFw5ttajYUIuSwX+T CVLCKRHESiDZV4Ez7OZQUAdtJPnJTcEWmD/bwMgpLDwb6qY+P1eai5I/ZCd5q7Fa rUQMFqneI0KePb0cLHLZAdfFBAVZzY8pHR1+sKyQ7UFmITFb5uWCEkIW7yOo0a3G UBFftFYAPj+oqwGdz/RMDHrZ0GFAVBSaAotBHvsIr9bqrpkvX1u4toC+RNF/xVb8 lYaIoFsZASQPZ8zopuiQ+/4c60k9895Y1fg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdehleejlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecufghrlhcuvffnffculdefhedmnecujfgurhepfffhvfevuf fkfhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgv rhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpe egffejvefgveduvdejtddvtdeijeehudeuledvudeftdfgfeejvdekveekiedvvdenucff ohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiih iidpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepth hglhesshhsshdrphhghhdrphgrrdhushdprhgtphhtthhopehpghhsqhhlqdgtohhmmhhi thhtvghrsheslhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 20 Apr 2026 19:03:00 -0400 (EDT) Date: Tue, 21 Apr 2026 08:02:55 +0900 From: Michael Paquier To: Tom Lane Cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Clean up all relid fields of RestrictInfos during join removal. Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jp/wYgCe/4X/etuk" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --jp/wYgCe/4X/etuk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Tom, On Mon, Apr 20, 2026 at 06:48:35PM +0000, Tom Lane wrote: > Clean up all relid fields of RestrictInfos during join removal. >=20 > The original implementation of remove_rel_from_restrictinfo() > thought it could skate by with removing no-longer-valid relid > bits from only the clause_relids and required_relids fields. > This is quite bogus, although somehow we had not run across a > counterexample before now. At minimum, the left_relids and > right_relids fields need to be fixed because they will be > examined later by clause_sides_match_join(). But it seems > pretty foolish not to fix all the relid fields, so do that. prion looks unhappy on this one: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dprion&dt=3D2026-0= 4-20%2022%3A50%3A01 This uses -DRELCACHE_FORCE_RELEASE -DCATCACHE_FORCE_RELEASE. -- Michael --jp/wYgCe/4X/etuk Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmnmsJ8ACgkQnvQgOdby QH0vfhAAmaRyfl3I+ARHw1rtkz3NDI4zeLRJZRF3RwxlsGiXWAWD8W5vUXKVeUkD Zm4VFr7uq+Q4gku4QjGbzFhFeSVxXz/F+aMEhOAJBCsBddKFwgsEy879X4f0ECgn 8AbWlhBBODmzjp7IBpK6tPtE0ZbXN7pHsdPqtujRLTvIzJfhcWG8L+PNzKbq8xPp rErdM+htSZHgUj90AqL0jMD20oyqbRno+JFXcZXuEUwfwwtbZoafJQ7ruEoFj7fo Dwo5BQazcE3mqUayFtS8I92fw7qBBRVSVwioxUCsx488dVAE17oo8G+cqBHFBHBy dRioeJZ4TKchTht+UiQzx/4PfvMeMhpIs9Fr4UY39wQCqcE0ccmZzWYtYRPqqt/o ON28wvYqMhXNOKM5Ut3GK3gl1XAeZrUCTPncQmndOiC66BY8e3cL/abc59p7ogvl Ay2/P/BKY+20wL8SIn8GfgEX5URQYTzYet/DJrDK4Vxq446FW/tKZxpAqa/5cJry SO4RpUFKOblgAVXSlGMkWC7lPYbi3xIboWop6BSPKEzQ2EctxvP4MGQHrOsJ4i2+ Q2Dg923otf1XAs7SyyjrVhAsoTF9COPL08coKNySIyvgud6fy0N8lRUSJ2PZ0Jkr eit0hr8sWZ+Cepga4TliLn7mSU5EBk/rmzjVbz5BiKw5ppTr//U= =5yzA -----END PGP SIGNATURE----- --jp/wYgCe/4X/etuk--