From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: introduce dynamic shared memory registry |
Date: | 2023-12-19 16:19:11 |
Message-ID: | 20231219161911.GE831499@nathanxps13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Dec 08, 2023 at 04:36:52PM +0900, Michael Paquier wrote:
> Yes, tracking that in a more central way can have many usages, so your
> patch sounds like a good idea. Note that we have one case in core
> that be improved and make use of what you have here: autoprewarm.c.
I'll add a patch for autoprewarm.c. Even if we don't proceed with that
change, it'll be a good demonstration.
> +dsm_registry_init_or_attach(const char *key, void **ptr, size_t size,
> + void (*init_callback) (void *ptr))
>
> This is shaped around dshash_find_or_insert(), but it looks like you'd
> want an equivalent for dshash_find(), as well.
What is the use-case for only verifying the existence of a segment?
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Ishaan Adarsh | 2023-12-19 16:26:01 | Re: [DOC] Introducing Quick Start Guide to PL/pgSQL and PL/Python Documentation |
Previous Message | Nathan Bossart | 2023-12-19 16:14:44 | Re: introduce dynamic shared memory registry |