Re: Use boolean array for nulls parameters

From: japin <japinli(at)hotmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Use boolean array for nulls parameters
Date: 2021-01-20 02:26:19
Message-ID: MEYP282MB16690D09E64EC8442AD61E4BB6A20@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Tue, 19 Jan 2021 at 23:45, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> japin <japinli(at)hotmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2021-01-20 02:28:54 Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Previous Message Tatsuro Yamada 2021-01-20 02:05:54 Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?