| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Clough <Greg(dot)Clough(at)ihsmarkit(dot)com> |
| Cc: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: database crash during pgbench run |
| Date: | 2018-12-11 16:01:14 |
| Message-ID: | 10578.1544544074@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Greg Clough <Greg(dot)Clough(at)ihsmarkit(dot)com> writes:
>>> 2018-12-10 19:11:56 IST 23647 LOG: received fast shutdown request
>>> any idea what can cause it ?
>> Something sent SIGINT to the postmaster.
> My money is on the OoM (Out of Memory) killer.
That usually uses SIGKILL. If I had to guess, I'd wonder whether the
postmaster was manually started, and if so whether it was properly
dissociated from the user's terminal (with nohup or the like).
If it wasn't, then a control-C typed at the terminal would SIGINT the
postmaster as well as whatever it was meant to terminate.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2018-12-11 18:55:31 | Re: Database size 1T but unclear why |
| Previous Message | Greg Clough | 2018-12-11 14:35:20 | RE: database crash during pgbench run |