<div dir="ltr">We're running streaming replication on <span style="color:rgb(0,0,0);font-size:12px">PostgreSQL 9.2 </span>and we occasionally hit the well-known "<font color="#000000"><span style="font-size:12px">canceling statement due to conflict with recovery" error whenever a slave gets too far behind. Since this error is seemingly triggered on unrelated queries that happen to still be running at the same time as the offending long-running query, it's difficult to make all parts of our code resilient to this problem.</span></font><div>
<span style="color:rgb(0,0,0);font-size:12px"><br></span></div><div style><span style="color:rgb(0,0,0);font-size:12px">I'd like to suggest that pgpool add optional retry logic that could be configured to automatically repeat a query up to a specified number of times if the database triggers that specific error message. Opinions?</span></div>
<div style><span style="color:rgb(0,0,0);font-size:12px"><br></span></div><div style><span style="color:rgb(0,0,0);font-size:12px"><br></span></div><div style><span style="color:rgb(0,0,0);font-size:12px">Jeff</span></div>
</div>