Re: Eliminating SPI / SQL from some RI triggers - take 3

On Tue, Mar 31, 2026 at 10:33 PM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> On 3/31/26 13:35, Daniel Gustafsson wrote:
> >> On 31 Mar 2026, at 13:26, Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> >>
> >> On Tue, Mar 31, 2026 at 8:22 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> >>>> On 31 Mar 2026, at 12:57, Junwang Zhao <zhjwpku(at)gmail(dot)com> 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).

I see, thanks for checking that.

--
Thanks, Amit Langote