fix(backend): Skip interconnect initialization for auxiliary background workers #1457
+7
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses Issue #1389 by preventing auxiliary background worker processes from opening unnecessary network sockets during interconnect initialization.
Problem
Auxiliary background workers (ftsprobe, global deadlock detector, dtx recovery, sweeper, pg_cron launcher, ic proxy) were initializing the Motion Layer IPC, which opens network sockets for data exchange. Since these processes don't require interconnect communication, this behavior is unnecessary and can be considered a security concern.
Solution
Added a check for
amAuxiliaryBgWorker()in bothcdb_setup()andcdb_cleanup()functions to skip interconnect initialization and cleanup for auxiliary background workers.Changes:
src/backend/cdb/cdbutil.c:!amAuxiliaryBgWorker()condition tocdb_setup()to skipInitMotionLayerIPC()call!amAuxiliaryBgWorker()condition tocdb_cleanup()to skipCleanUpMotionLayerIPC()call#ifdef USE_INTERNAL_FTSand#elsecode pathsTesting
postmaster/postmaster.halready included in cdbutil.camAuxiliaryBgWorker()properly declared in postmaster.hFixes #1389