| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(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:04:58 |
| Message-ID: | CALj2ACVX8CTHZ3ZCa-fqOW-sBRjsz77daudB7_k9oceZaHbyeg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 8, 2022 at 2:30 PM John Naylor <john(dot)naylor(at)enterprisedb(dot)com> wrote:
>
> On Mon, Aug 8, 2022 at 2:26 PM Bharath Rupireddy
> <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> > 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.
I haven't looked upthread, please share the difference. How about
another version of the function that returns the index too?
--
Bharath Rupireddy
RDS Open Source Databases: https://aws.amazon.com/rds/postgresql/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2022-08-08 09:23:28 | Re: Skipping schema changes in publication |
| Previous Message | John Naylor | 2022-08-08 09:00:11 | Re: optimize lookups in snapshot [sub]xip arrays |