| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | aleksandr(dot)newray(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15697: Restarting the server because of the error checkpointer |
| Date: | 2019-03-16 14:14:09 |
| Message-ID: | 13646.1552745649@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> I have a website using postgresql on my vps. I get an error restarting
> postgresql server:
> 2019-03-15 05:58:53.305 UTC [1329] LOG: shutting down
> 2019-03-15 05:58:53.313 UTC [1311] LOG: checkpointer process (PID 1329)
> exited with exit code 0
> 2019-03-15 05:58:53.313 UTC [1311] LOG: terminating any other active server
> processes
Taking this at face value, it says that the checkpointer child process
exited before it was supposed to. Given that it exited with exit(0),
that seems to mean that something sent it SIGUSR2, which is the
normal-shutdown signal that the postmaster would have sent it later on.
It's difficult to say anything beyond that on this much evidence,
but I suspect that there are moving parts you haven't told us about.
Are you using a nonstandard shutdown script? Maybe there are poorly-
debugged extensions installed?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-03-16 14:46:42 | Re: BUG #15696: year field of interval type is not rounded to nearest integer |
| Previous Message | PG Bug reporting form | 2019-03-16 07:59:13 | BUG #15697: Restarting the server because of the error checkpointer |