Re: introduce dynamic shared memory registry
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org
Date: 2024-01-06T16:35:16Z
Lists: pgsql-hackers
Attachments
- v5-0001-add-dsm-registry.patch (text/x-diff)
On Sat, Jan 06, 2024 at 07:34:15PM +0530, Bharath Rupireddy wrote: > 1. Update all the copyright to the new year. A run of > src/tools/copyright.pl on the source tree will take care of it at some > point, but still it's good if we can update while we are here. Done. > 2. Typo: missing "an" before "already-attached". > + /* Return address of already-attached DSM registry entry. */ Done. > 3. Use NAMEDATALEN instead of 64? > + char key[64]; I kept this the same, as I didn't see any need to tie the key size to NAMEDATALEN. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
Commits
-
Fix possible NULL pointer dereference in GetNamedDSMSegment().
- 4372adfa24f2 17.0 landed
-
Teach autoprewarm to use the dynamic shared memory registry.
- abb0b4fc03fc 17.0 landed
-
Introduce the dynamic shared memory registry.
- 8b2bcf3f287c 17.0 landed
-
doc: Reorganize section for shared memory and LWLocks.
- 964152c476f2 17.0 landed