| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, alex work <alexwork033(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Slow GRANT ROLE on PostgreSQL 16 with thousands of ROLEs |
| Date: | 2024-03-22 01:03:32 |
| Message-ID: | 20240322010332.GA2109205@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, Mar 21, 2024 at 08:59:54PM -0400, Tom Lane wrote:
> However ... I just remembered that we have a Bloom filter implementation
> in core now (src/backend/lib/bloomfilter.c). How about using that
> to quickly reject (hopefully) most role OIDs, and only do the
> list_member_oid check if the filter passes?
Seems worth a try. I've been looking for an excuse to use that...
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-03-22 01:52:51 | Re: Slow GRANT ROLE on PostgreSQL 16 with thousands of ROLEs |
| Previous Message | Tom Lane | 2024-03-22 00:59:54 | Re: Slow GRANT ROLE on PostgreSQL 16 with thousands of ROLEs |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2024-03-22 01:12:48 | Re: Catalog domain not-null constraints |
| Previous Message | Tom Lane | 2024-03-22 00:59:54 | Re: Slow GRANT ROLE on PostgreSQL 16 with thousands of ROLEs |