| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Justin King <kingpin867(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: walreceiver termination |
| Date: | 2020-04-23 17:47:48 |
| Message-ID: | 18350.1587664068@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Justin King <kingpin867(at)gmail(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dummy Account | 2020-04-23 18:18:43 | Could Not Connect To Server |
| Previous Message | Paul Jungwirth | 2020-04-23 17:26:20 | Re: Reg: Help to understand the source code |