database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

Improve handling of OOM score adjustment in sample Linux start script.

Browse Source 
Per a suggestion from Christoph Berg.
This commit is contained in:
Tom Lane 2014-07-01 17:23:16 -04:00
parent 5a421a47eb
commit f23425fa95
1 changed files with 19 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
contrib/start-scripts/linux
View File

@ -42,18 +42,17 @@ PGLOG="$PGDATA/serverlog"
# It's often a good idea to protect the postmaster from being killed by the # It's often a good idea to protect the postmaster from being killed by the
# OOM killer (which will tend to preferentially kill the postmaster because # OOM killer (which will tend to preferentially kill the postmaster because
# of the way it accounts for shared memory). Setting the OOM_SCORE_ADJ value # of the way it accounts for shared memory). To do that, uncomment these
# to -1000 will disable OOM kill altogether, which is a good thing for the # three lines:
# postmaster, but not so much for individual backends. If you enable this, #PG_OOM_ADJUST_FILE=/proc/self/oom_score_adj
# also uncomment the DAEMON_ENV line, which will instruct backends to set #PG_MASTER_OOM_SCORE_ADJ=-1000
# their OOM adjustments back to the default setting of zero. #PG_CHILD_OOM_SCORE_ADJ=0
#OOM_SCORE_ADJ=-1000
#DAEMON_ENV="PG_OOM_ADJUST_FILE=/proc/self/oom_score_adj"
# Older Linux kernels may not have /proc/self/oom_score_adj, but instead # Older Linux kernels may not have /proc/self/oom_score_adj, but instead
# /proc/self/oom_adj, which works similarly except the disable value is -17. # /proc/self/oom_adj, which works similarly except for having a different
# For such a system, uncomment these two lines instead. # range of scores. For such a system, uncomment these three lines instead:
#OOM_ADJ=-17 #PG_OOM_ADJUST_FILE=/proc/self/oom_adj
#DAEMON_ENV="PG_OOM_ADJUST_FILE=/proc/self/oom_adj" #PG_MASTER_OOM_SCORE_ADJ=-17
#PG_CHILD_OOM_SCORE_ADJ=0
## STOP EDITING HERE ## STOP EDITING HERE
@ -80,13 +79,19 @@ test -x $DAEMON ||
fi fi
} }
# If we want to tell child processes to adjust their OOM scores, set up the
# necessary environment variables. Can't just export them through the "su".
if [ -e "$PG_OOM_ADJUST_FILE" -a -n "PG_CHILD_OOM_SCORE_ADJ" ]
then
DAEMON_ENV="PG_OOM_ADJUST_FILE=$PG_OOM_ADJUST_FILE PG_OOM_ADJUST_VALUE=$PG_CHILD_OOM_SCORE_ADJ"
fi
# Parse command line parameters. # Parse command line parameters.
case $1 in case $1 in
start) start)
echo -n "Starting PostgreSQL: " echo -n "Starting PostgreSQL: "
test x"$OOM_SCORE_ADJ" != x && echo "$OOM_SCORE_ADJ" > /proc/self/oom_score_adj test -e "$PG_OOM_ADJUST_FILE" && echo "$PG_MASTER_OOM_SCORE_ADJ" > "$PG_OOM_ADJUST_FILE"
test x"$OOM_ADJ" != x && echo "$OOM_ADJ" > /proc/self/oom_adj
su - $PGUSER -c "$DAEMON_ENV $DAEMON -D '$PGDATA' &" >>$PGLOG 2>&1 su - $PGUSER -c "$DAEMON_ENV $DAEMON -D '$PGDATA' &" >>$PGLOG 2>&1
echo "ok" echo "ok"
;; ;;
@ -98,8 +103,7 @@ case $1 in
restart) restart)
echo -n "Restarting PostgreSQL: " echo -n "Restarting PostgreSQL: "
su - $PGUSER -c "$PGCTL stop -D '$PGDATA' -s -m fast -w" su - $PGUSER -c "$PGCTL stop -D '$PGDATA' -s -m fast -w"
test x"$OOM_SCORE_ADJ" != x && echo "$OOM_SCORE_ADJ" > /proc/self/oom_score_adj test -e "$PG_OOM_ADJUST_FILE" && echo "$PG_MASTER_OOM_SCORE_ADJ" > "$PG_OOM_ADJUST_FILE"
test x"$OOM_ADJ" != x && echo "$OOM_ADJ" > /proc/self/oom_adj
su - $PGUSER -c "$DAEMON_ENV $DAEMON -D '$PGDATA' &" >>$PGLOG 2>&1 su - $PGUSER -c "$DAEMON_ENV $DAEMON -D '$PGDATA' &" >>$PGLOG 2>&1
echo "ok" echo "ok"
;; ;;