On 29.06.23 01:36, Michael Paquier wrote:
> While working on a different patch, I have noted three code paths that
> call changeDependencyFor() but don't check that they do not return
> errors. In all the three cases (support function, extension/schema
> and object/schema), it seems to me that only one dependency update is
> expected.
Why can't changeDependencyFor() raise the error itself?