Re: shmem_startup_hook called twice on Windows
Sami Imseih <samimseih@gmail.com>
From: Sami Imseih <samimseih@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-09-08T21:31:43Z
Lists: pgsql-hackers
> I quickly put together a patch for the stuff we've discussed in this > thread. WDYT? > > -- > nathan I still think we need to mention EXEC_BACKEND somehow. The way it's done in [0], it says "On Windows (and anywhere else where EXEC_BACKEND is defined)" So we do have precedent of mentioning EXEC_BACKEND in docs, and it’s clearer than the ambiguity of saying 'on some builds'/'in other builds'. [0] https://www.postgresql.org/docs/current/bgworker.html -- Sami
Commits
-
Fix documentation for shmem_startup_hook.
- d96c854dfc63 19 (unreleased) landed
- a80b7a0547da 18.0 landed
- 778f391c26c6 17.7 landed
-
test_slru: Fix LWLock tranche allocation in EXEC_BACKEND builds.
- 530cfa8eb50c 19 (unreleased) landed
-
doc: Reorganize section for shared memory and LWLocks.
- 964152c476f2 17.0 cited
-
Refactor CreateSharedMemoryAndSemaphores
- 69d903367cde 17.0 cited