| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, John Naylor <jcnaylor(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: optimize lookups in snapshot [sub]xip arrays |
| Date: | 2022-08-08 09:00:11 |
| Message-ID: | CAFBsxsHO8UrtrhqDNoOPQ3Ufbu9i0+WFxKaTeyBMLYv-HqdTUg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 8, 2022 at 2:26 PM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2022-08-08 09:04:58 | Re: optimize lookups in snapshot [sub]xip arrays |
| Previous Message | Kyotaro Horiguchi | 2022-08-08 08:56:44 | Re: logical decoding and replication of sequences |