| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Moshe Jacobson <moshe(at)neadwerx(dot)com> |
| Subject: | Re: Cache lookup errors with functions manipulation object addresses |
| Date: | 2017-07-20 14:07:16 |
| Message-ID: | CAB7nPqTvwKE1k2qsNRAfEWxae0eFh4ntVKyRpTobXMt4pKeSOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 20, 2017 at 4:04 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2017-07-20 14:11:20 | Re: autovacuum can't keep up, bloat just continues to rise |
| Previous Message | Alvaro Herrera | 2017-07-20 14:04:02 | Re: Cache lookup errors with functions manipulation object addresses |