have you set ```max_standby_streaming_delay``? The default is 30 seconds, which means that this will be the maximum time allowed for a replication lag caused by a conflicting query.
Yes, we've bumped that up a lot.
You can use ``hot_standby_feedback = on``, but the downside will be more bloat on the tables.
I'm not sure I understand. I'm not worried about the query being cancelled on the replica. max_standby_streaming_delay fixes that for us. I'm worried about the streaming replication being paused while this table scan is running. If the table scan takes several minutes, then the replica becomes several minutes out of sync with the master. I'd prefer that not to happen and I'm wondering if there's a way to do that.