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

From Alvaro Herrera
Subject Re: [HACKERS] Cache lookup errors with functions manipulation objectaddresses
Date
Msg-id 20170720162623.ei4f3qgn4zzxxa3q@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] Cache lookup errors with functions manipulation object addresses  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Cache lookup errors with functions manipulation object addresses
List pgsql-hackers
Michael Paquier wrote:
> 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.

I think minimizing API churn is worthwhile in some cases but not all.
These functions seem fringe enough that not having an API-compatible
version is unnecessary.  But that's just my opinion.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Sokolov Yura
Date:
Subject: Re: [HACKERS] Increase Vacuum ring buffer.
Next
From: Alik Khilazhev
Date:
Subject: Re: [HACKERS] [WIP] Zipfian distribution in pgbench