From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Document DSM Registry |
Date: | 2025-10-06 19:38:01 |
Message-ID: | aOQamT4fBf0Jw51I@nathan |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
- <title>Requesting Shared Memory After Startup</title>
+ <title>DSM Registry</title>
I'm -1 for renaming the section like this. The existing title makes the
purpose clear and is symmetrical with the section above it. I don't see a
need to expose the current implementation's name, either.
+ It supports creating named DSM segments with <function>GetNamedDSMSegment</function>,
+ named dynamic shared memory areas (DSAs) with <function>GetNamedDSA</function>,
+ and named hash tables backed by a DSA with <function>GetNamedDSHash</function>.
IMHO we should provide more details about DSAs and dshash tables.
One of the reasons I didn't add GetNamedDSA() and GetNamedDSHash() to these
docs was because there's no documentation for ShmemInitHash(), either. Can
we add something for that, too?
--
nathan
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2025-10-06 20:00:10 | Re: Invalid pointer access in logical decoding after error |
Previous Message | Robert Haas | 2025-10-06 19:36:49 | Re: plan shape work |