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 1w7ZEM-005Ryx-2t for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Mar 2026 13:34:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w7ZEL-00APUC-1B for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Mar 2026 13:34:05 +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.96) (envelope-from ) id 1w7ZEL-00APU4-0E for pgsql-hackers@lists.postgresql.org; Tue, 31 Mar 2026 13:34:05 +0000 Received: from relay2-d.mail.gandi.net ([2001:4b98:dc4:8::222]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w7ZEJ-00000001yUI-1gNN for pgsql-hackers@postgresql.org; Tue, 31 Mar 2026 13:34:04 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id B10793EBD7; Tue, 31 Mar 2026 13:33:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1774964035; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KUekhyQRBDRDaN9u1jaSvmNqZqH9YOdbwdnR+Fn5LOc=; b=f/iZU0wJZmBe3H1EOIMmvMhFDGgw0mqWNbBCy7Lsb4rkSXAiHgistTWJhTU4Pactn3WqJO MaFPRd4XJ6vks4+w8H4sZfLC5wVQy+5PwkFpA/a4ZHQHA7GcvjWcA+VfgyogSA/icyxhD1 fInvsdIGbyz0SY6Ej+wyBpjBd5S1oV97V9Q6hTxwGd2qpG+5GGoqv6fycwLDLLyUvX/+dQ GkRfhUrdQGjLvuZaz4r7NCLP3jS2uH3yHc/PTg0qhnGfx8ZmGyyI/F0t21Bg3M0HBBr4Vj yHCUcAt6qb2oIEiPYelW0mFubBRL7Q1cFMNkSgskl0aSuWooFqe8QnSF6V87sw== Message-ID: Date: Tue, 31 Mar 2026 15:33:53 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Eliminating SPI / SQL from some RI triggers - take 3 To: Daniel Gustafsson , Amit Langote Cc: Junwang Zhao , Chao Li , Haibo Yan , Pavel Stehule , PostgreSQL Hackers References: <2BE661BA-D909-4093-BF78-DB9B0C099337@gmail.com> <77FA04FE-1F84-4DA1-8855-8BBFD8CC889A@gmail.com> <5761CE63-06B8-49D9-BAF4-D921F64F18B1@yesql.se> Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-GND-Sasl: tomas@vondra.me X-GND-Cause: dmFkZTEUOKPsmpkLw7LUeowu2vny4Zitp/LlV/OmA/kG5/cVmGiVKZ+edamBokgu6oqnhkJ15u+Hye27NM1kLktSiRyOsSDarBb71Dvo6W2pgu6ygdkYf9yTATlW5GSN9tDylOz6Q13ar5BsLoe6DTIwrdFChB7ClcZ/A2xtl7++KWWg0wOHvdh8JuxeLrw22mWmuEYHqo39Fzw69TRQfdYzNP/aGFHuLuE3YG6QKVdn3Zb8935n1UOvNfH8QEJ+0oowURmTZfVVI6Cl+rd3oEpxd97Yv8vVwWxFAj7sm/teuQO0VgIRF1jRN+1WHhZn/YWRxM0KLp83Y4Gg6CE2pRn9tWjbRNwDtoWdGIGhWmzb/ahGAA/89aD0Hc7OoUMlc/xKh2Did7KIGaY5CRqgdkpQsIMikVRuPasn8LZSlomgGDNV7qbd1b+K44pK3jEDvqC3WedjiqJdMWVUIkfy6qYRwJSgOrtSEaqZhQ6PchGIkG8KQbWrOBmYmDhvRypT+SwEHxDCRTUC0ObmY8/I4Ss3S6N1Exy2G/xqAQc1YLP4a3mKNTzQ98h3HZJ+bvOQcpsJJiDJzNHZmbiY/ZmLX68/sm9hYYNY7qpH/r+yvGF4BDCfNZgZIR42pBkZ1qduZX22WgeFLzbo/PmOTwTrWc/RMCkA2Twe/+vaUlF+AKN0iylpLg X-GND-State: clean X-GND-Score: -100 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 3/31/26 13:35, Daniel Gustafsson wrote: >> On 31 Mar 2026, at 13:26, Amit Langote wrote: >> >> On Tue, Mar 31, 2026 at 8:22 PM Daniel Gustafsson wrote: >>>> On 31 Mar 2026, at 12:57, Junwang Zhao wrote: >>> >>>> prion is happy now, the fix works, thanks. >>> >>> The widowbird failure seems to be SPI related as well, relevant portion of log >>> below. Is that the same or another error? >> >> prion was unhappy about something else, which I've fixed: >> https://www.postgresql.org/message-id/E1w7U6V-002H6n-0o%40gemulon.postgresql.org >> >> Though, I'm not sure if or why the fix is now the reason for >> widowbird's failure. >> Right, that failure doesn't seem related. It first appeared ~2 weeks ago, i.e. before this got committed. I don't know what triggered it. It might even be a simple timing issue. This is a rpi4 machine, running from a USB flashdrive, so it's pretty slow, and a processes can occasionally "hang" for a little bit and not disconnect quick enough. Not sure if something changed ~2 weeks ago. It might also be the flash drive getting flaky (even though I don't see anything in dmesg). Anyway, this is likely unrelated to the commit. regards -- Tomas Vondra