Re: [HACKERS] Cache lookup errors with functions manipulation object addresses - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Cache lookup errors with functions manipulation object addresses
Date
Msg-id CAB7nPqTvwKE1k2qsNRAfEWxae0eFh4ntVKyRpTobXMt4pKeSOA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Cache lookup errors with functions manipulation objectaddresses  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [HACKERS] Cache lookup errors with functions manipulation objectaddresses
List pgsql-hackers
On Thu, Jul 20, 2017 at 4:04 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> I think the addition of checks everywhere for NULL return is worse.
> Let's add a missing_ok flag instead, so that most callers can just trust
> that they get a non null value if they don't want to deal with that
> case.

If you want to minimize the diffs or such a patch, we could as well
have an extended version of those APIs. I don't think that for the
addition of one argument like a missing_ok that's the way to go, but
some people may like that to make this patch less intrusive.
-- 
Michael



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Cache lookup errors with functions manipulation objectaddresses
Next
From: "Joshua D. Drake"
Date:
Subject: Re: [HACKERS] autovacuum can't keep up, bloat just continues to rise