Re: Add more sanity checks around callers of changeDependencyFor()

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add more sanity checks around callers of changeDependencyFor()
Date: 2023-07-06 16:41:49
Message-ID: 37381c7f-3f9a-c23b-47a9-211220afca70@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-07-06 16:51:56 Re: Avoid overflow with simplehash
Previous Message Ranier Vilela 2023-07-06 16:40:00 Re: Avoid overflow with simplehash