Folks, Is there a way to limit or disable retries of failed updates in the write-behind store? I can't find one, it looks like if an update fails, it is moved to the end of the queue and then eventually retried. If it fails again, process is repeated.
Such behavior *might* be OK if failures are caused by database being temporarily unavailable. But what if update fails deterministically, for example due to a constraint violation? There is absolutely no reason to retry it, and at the same time it can cause stability and performance issues when buffer is full with such "broken" updates. Does it makes sense to add an option that would allow to limit number of retries (or even disable them)? -Val
