> On Dec 5, 2021, at 10:56 PM, osumi.takami...@fujitsu.com wrote:
>
> In my humble opinion, I felt the original purpose of the patch was to
> partially remedy
> the situation that during the failure of apply, the apply process keeps going
> into the infinite error loop.
I agree.
> I'd say that in this sense, if we include such resource errors, we fail to
> achieve
> the purpose in some cases, because of some left possibilities of infinite
> loop.
> Disabling the subscription with even one any error excludes this irregular
> possibility,
> since there's no room to continue the infinite loop.
I don't think there is any right answer here. It's a question of policy
preferences.
My concern about disabling a subscription in response to *any* error is that
people may find the feature does more harm than good. Disabling the
subscription in response to an occasional deadlock against other database
users, or occasional resource pressure, might annoy people and lead to the
feature simply not being used.
I am happy to defer to your policy preference. Thanks for your work on the
patch!
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
