Re: using SysCacheGetAttrNotNull in place of heap_getattr - Mailing list pgsql-hackers

From Tom Lane
Subject Re: using SysCacheGetAttrNotNull in place of heap_getattr
Date
Msg-id 3366977.1692810266@sss.pgh.pa.us
Whole thread Raw
In response to using SysCacheGetAttrNotNull in place of heap_getattr  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> I was about to push a quick patch to replace the use of heap_getattr()
> in get_primary_key_attnos() with SysCacheGetAttrNotNull(), because that
> makes the code a few lines shorter and AFAICS there's no downside.
> However, I realized that the commit that added the function
> (d435f15fff3c) did not make any such change at all -- it only changed
> SysCacheGetAttr calls to use the new function, but no heap_getattr.
> And we don't seem to have added such calls after.

Seems to me it'd be more consistent to invent a wrapper function
heap_getattr_notnull() that adds the same sort of error check,
instead of abusing the syscache function as you suggest.  For one
thing, then the functionality could be used whether there's a
suitable syscache or not.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: PG 16 draft release notes ready
Next
From: Alvaro Herrera
Date:
Subject: Re: cataloguing NOT NULL constraints