Re: Use boolean array for nulls parameters - Mailing list pgsql-hackers

From japin
Subject Re: Use boolean array for nulls parameters
Date
Msg-id MEYP282MB16690D09E64EC8442AD61E4BB6A20@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Use boolean array for nulls parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 19 Jan 2021 at 23:45, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> japin <japinli@hotmail.com> writes:
>> When I review the [1], I find that the tuple's nulls array use char type.
>> However there are many places use boolean array to repsent the nulls array,
>> so I think we can replace the char type nulls array to boolean type.  This
>> change will break the SPI_xxx API, I'm not sure whether this chagnges cause
>> other problems or not.  Any thought?
>
> We have always considered that changing the APIs of published SPI
> interfaces is a non-starter.  The entire reason those calls still
> exist at all is for the benefit of third-party extensions.
>

Thanks for your clarify.  I agree that we should keep the APIs stable, maybe we
can modify this in someday when the APIs must be changed.

-- 
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.



pgsql-hackers by date:

Previous
From: Tatsuro Yamada
Date:
Subject: Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Next
From: Julien Rouhaud
Date:
Subject: Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?