pgsql: Clear MyProc and MyProcSignalState before they become invalid.

Clear MyProc and MyProcSignalState before they become invalid.

Evidence from buildfarm member crake suggests that the new test_shm_mq
module is routinely crashing the server due to the arrival of a SIGUSR1
after the shared memory segment has been unmapped.  Although processes
using the new dynamic background worker facilities are more likely to
receive a SIGUSR1 around this time, the problem is also possible on older
branches, so I'm back-patching the parts of this change that apply to
older branches as far as they apply.

It's already generally the case that code checks whether these pointers
are NULL before deferencing them, so the important thing is mostly to
make sure that they do get set to NULL before they become invalid.  But
in master, there's one case in procsignal_sigusr1_handler that lacks a
NULL guard, so add that.

Patch by me; review by Tom Lane.

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/5d807a74bf66ba9fb4f55e49e7c601b0b9804123

Modified Files
--------------
src/backend/storage/ipc/procsignal.c |    7 ++++++
src/backend/storage/lmgr/proc.c      |   42 ++++++++++++++++++++--------------
2 files changed, 32 insertions(+), 17 deletions(-)