[pgpool-general: 1568] Automatic retry on canceled statements

[Jeff Lawson]

We're running streaming replication on PostgreSQL 9.2 and we occasionally
hit the well-known "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.

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?


Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20130404/f7c9a789/attachment.htm>