Justin King <kingpin867@xxxxxxxxx> writes: > We've seen unexpected termination of the WAL receiver process. This > stops streaming replication, but the replica stays available -- > restarting the server resumes streaming replication where it left off. > We've seen this across nearly every recent version of PG, (9.4, 9.5, > 11.x, 12.x) -- anything omitted is one we haven't used. > I don't have an explanation for the cause, but I was able to set > logging to "debug5" and run an strace of the walrecevier PID when it > eventually happened. It appears as if the SIGTERM is coming from the > "postgres: startup" process. The startup process intentionally SIGTERMs the walreceiver under various circumstances, so I'm not sure that there's any surprise here. Have you checked the postmaster log? regards, tom lane
