| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | carlos(dot)gonzalez(at)nologin(dot)es |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17666: Unexpected shutdown |
| Date: | 2022-10-27 13:22:34 |
| Message-ID: | 642795.1666876954@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:
> Last October 2nd the postgresql service shut down the database
> unexpectedly.
> We only have this entry in the log file. Please, is there any way to
> investigate the problem with so little information?
> 2022-10-02 04:33:18.884 CDT pid: [9246] db: user: id: 6231c4b5.241e
> sqlstate: 00000 > LOG: received immediate shutdown request
That is a commanded shutdown: something sent the postmaster process
a SIGQUIT signal. The cause is very unlikely to be within Postgres
itself. You should be thinking in terms of operator error or a
misbehaving administrative script.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-10-27 13:49:18 | BUG #17668: Query normalization generates multiple queryId:s for calls to the same procedure |
| Previous Message | Japin Li | 2022-10-27 12:59:18 | Re: BUG #17667: to_char is used to collect statistics by week |