Each WAL redo process creates a tiny DSM segment, like /dev/shm/PostgreSQL.3449905360. They are not always (never?) cleaned up on exit, not even on pageserver restart, so a pageserver host can accumulate tens of thousands of these files over time. Each file is small, 3-5 kB, but they add up to a lot of wasted memory over time.
A WAL redo process should not need DSM for anything, so let's remove the DSM initialization step altogether, so that the files are not created in the first place.
Each WAL redo process creates a tiny DSM segment, like
/dev/shm/PostgreSQL.3449905360
. They are not always (never?) cleaned up on exit, not even on pageserver restart, so a pageserver host can accumulate tens of thousands of these files over time. Each file is small, 3-5 kB, but they add up to a lot of wasted memory over time.slack discussion: https://neondb.slack.com/archives/C033RQ5SPDH/p1731486990179549?thread_ts=1731445405.348699&cid=C033RQ5SPDH
A WAL redo process should not need DSM for anything, so let's remove the DSM initialization step altogether, so that the files are not created in the first place.