ERROR: canceling statement due to conflict with recovery

Hello all,

Your expertise is needed on this. I was going through previous mails
regarding the same topic and was able to setup the slave with
hot_standby_feedback enabled.
Queries are running fine with bloat occuring on master.

I tried the below scenario, where i disabled hot_standby_feedback and on
table level disabled autovacuum for 2 big tables on master. Ran the query
on the slave machine but still conflict error occurs.

I checked the *pg_stat_database_conflicts* view, the counter is increasing
for *confl_snapshot*. Cross-checked with *pg_stat_user_tables* view, last
time autovacuum happened for the 2 tables was 1 day before.

My doubt, even though no autovacuum and no DML activities happening for
both the tables in master. Why is conflict error occuring?

Thanks & Regards,
Rajamohan.J