Re: Little cleanup of ShmemInit function names
Andreas Karlsson <andreas@proxel.se>
From: Andreas Karlsson <andreas@proxel.se>
To: Heikki Linnakangas <hlinnaka@iki.fi>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2024-08-28T15:26:38Z
Lists: pgsql-hackers
On 8/7/24 2:08 PM, Heikki Linnakangas wrote: > The attached patches rename them to follow the usual naming convention. > The InitLocks() function is refactored a bit more, splitting the > per-backend initialization to a separate InitLockManagerAccess() > function. That's why it's in a separate commit. I like the idea behind the patches. And they still apply and build. The first patch is clean and well commented. I just have two minor nitpicks. Small typo with the extra "which" which makes the sentence not flow correctly "This is called from CreateSharedMemoryAndSemaphores(), which see for more comments." On the topic of minor language issues I think the comma below is redundant. "In the normal postmaster case, the shared hash tables are created here." The second patch is a simple renaming which reduces mental load by making the naming more consistent so I like it. Also since these functions are not really useful for any extension authors I do not see any harm in renaming them. After cleaning up the language of that comment I think these patches can be committed. Andreas
Commits
-
Rename some shared memory initialization routines
- 478846e7688c 18.0 landed
-
Refactor lock manager initialization to make it a bit less special
- fbce7dfc77ea 18.0 landed