Comment 3 for bug 1649877

I have the same issue on RHEL 7.2, and UID set to (id -u postgres)
2011

I have below backups configured -
pg_basebackup --xlog -R -P --gzip --format=t
pg_backup_rotated.sh

postgresql (9.4.5) instance restarts with below error during backup times -

2017-03-19 19:00:21 EDT PANIC: semop(id=152698887) failed: Invalid argument
2017-03-19 19:00:21 EDT PANIC: semop(id=152698887) failed: Invalid argument
2017-03-19 19:00:26 EDT FATAL: semctl(152666118, 6, SETVAL, 0) failed: Invalid argument
2017-03-19 19:00:26 EDT LOG: server process (PID 13090) exited with exit code 1
2017-03-19 19:00:26 EDT LOG: terminating any other active server processes
2017-03-19 19:00:26 EDT WARNING: terminating connection because of crash of another server process
2017-03-19 19:00:26 EDT DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-03-19 19:00:26 EDT HINT: In a moment you should be able to reconnect to the database and repeat your command.
2017-03-19 19:00:26 EDT WARNING: terminating connection because of crash of another server process
2017-03-19 19:00:26 EDT DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-03-19 19:00:26 EDT HINT: In a moment you should be able to reconnect to the database and repeat your command.
2017-03-19 19:00:26 EDT WARNING: terminating connection because of crash of another server process
2017-03-19 19:00:26 EDT DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

memory.

Can you tell me what is the exact root cause of this issue?
Is it something related to user UID?