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 1wAnF2-000LD5-2E for pgsql-hackers@arkaria.postgresql.org; Thu, 09 Apr 2026 11:08:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wAnF0-005QQF-37 for pgsql-hackers@arkaria.postgresql.org; Thu, 09 Apr 2026 11:08:07 +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 1wAnF0-005QQ7-23 for pgsql-hackers@lists.postgresql.org; Thu, 09 Apr 2026 11:08:07 +0000 Received: from hst.kbt.io ([2001:41d0:8:9854::1]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wAnEy-00000000AW8-33wG for pgsql-hackers@postgresql.org; Thu, 09 Apr 2026 11:08:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kbt.io; s=default; t=1775732878; bh=bXM0rBlk+3MVe6bQwlkHlH+Ht6LMN7y3bL+h6VlWwTs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=GAAQUR2b4LF60samJIbFcPzr8QTHIs00PMpyh9lXIflnOaEQeiGXCM8I73egTyczh lU3FZq+1JEaE9Z8rvInT6patWZVfxwLULXhvxCBL+PnNZfrI/mvtSpLcs6YKlhr60u nJrSI/y19SmYl9szwW12C2FxYBqbr0fTFklJY1MQ0iY6aGyT6Dwb2Xa5HRooBL/BLr E05CnWyNHlogxBxa8klCo0iTdJxIQML6RFLnR1WYawKrcxgoIddh9sIE2gw8oPd5eO vnT/sA/AfxOI075evxVMD34Tt9YolSUFF9TkV++RG6NKTsPKeAIOTMf5SPB2eBsUoV oq/0w+RZvXPAw== Received: from hst.kbt.io (hst.kbt.io [IPv6:2001:41d0:8:9854::1]) by hst.kbt.io (Postfix) with ESMTPSA id 27A273C02AA; Thu, 9 Apr 2026 13:07:58 +0200 (CEST) Date: Thu, 9 Apr 2026 13:07:50 +0200 From: Sandro Santilli To: Tomas Vondra Cc: Amit Langote , Junwang Zhao , Pavel Stehule , PostgreSQL-development Subject: Re: Eliminating SPI / SQL from some RI triggers - take 3 Message-ID: Mail-Followup-To: Sandro Santilli , Tomas Vondra , Amit Langote , Junwang Zhao , Pavel Stehule , PostgreSQL-development References: <43b56e3b-80d6-4a45-a313-cb1caa587b22@vondra.me> <1290fac7-8430-4d2c-bfcb-00c65adff5e5@vondra.me> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jEGqOMWO3DrWfQ74" Content-Disposition: inline In-Reply-To: <1290fac7-8430-4d2c-bfcb-00c65adff5e5@vondra.me> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --jEGqOMWO3DrWfQ74 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 02, 2026 at 01:34:41PM +0100, Tomas Vondra wrote: >=20 > TBH I haven't noticed the memory context issue myself, I only noticed > because the builds with index prefetch started crashing. We're getting a crash in PostGIS too, since that commit was merged into the master branch, see https://trac.osgeo.org/postgis/ticket/6066 The crash is triggered a C function using SPI. --strk; --jEGqOMWO3DrWfQ74 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEyOAhc1XOBFGVnzBARwiVRt5AyacFAmnXiIQACgkQRwiVRt5A yafcKAv/Tp7dGIQuPyR4iK02dvqzze2Kc5iZzSJj+8BOQ1xOqGUgvkDY9njpboyH 9ErUtsN2SGrS7kgpqFLwy9S/B7bDa8rYUPQXMHAdKYMtArC+KU9RIKjM9D/RM6oE 5SJtHsNnBlvry4XMMtnfieoD1PdX8k4MvwRK9qWRd8vsmE7Sl7Jlfqu5XpnBXATy KCxykJ3Jam7+0sCxtvKlGR79n5TmV+SSys6/gJJsUYZnz/vAsD0+kqzI+rCuFpxG lTcx8Xf6YsCaToGijf54OoC23HYFrud66WfJWkTF1S+GFLGKqjgBZqja/aoxaQrF vg9yD/k5b8Ppg7aDvZW09jaXh0IA4ILcUJHaZCSuq168YSsJYwUmMtv26MKibl4L kZYFI+n6skG3gmOHdX9mi3o8WKO8SZSEIor4QsQApWsGpb0S4/7ifaIwXBOgPamh kVuq0wYIiwl82du5TdEkh7HMh2gyZivnLEWtBSUZF4g51PClqdsfbFkhPwEq7gSX W6j9o3L2 =bHnA -----END PGP SIGNATURE----- --jEGqOMWO3DrWfQ74--