Re: Use boolean array for nulls parameters

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: japin <japinli(at)hotmail(dot)com>
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-19 15:45:35
Message-ID: 480187.1611071135@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-01-19 15:57:25 Re: [PATCH 1/1] Fix detection of pwritev support for OSX.
Previous Message Tom Lane 2021-01-19 15:40:39 Re: TOAST condition for column size