On Mon, Aug 8, 2022 at 2:26 PM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
>
>
> 1) pg_lfind32 - why just uint32? If it's not possible to define
> functions for char, unsigned char, int16, uint16, int32, int64, uint64
> and so on, can we add a few comments around that? Also, the comments
Future work, as far as I'm concerned. I'm interested in using a char
version for json strings.
> 3) Can pg_lfind32 return the index of the key found, for instance to
> use it for setting/resetting the found element in the array?
That was just discussed. It's slightly faster not to return an index.
--
John Naylor
EDB: http://www.enterprisedb.com
