From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Clough <Greg.Clough@ihsmarkit.com>
cc: Mariel Cherkassky <mariel.cherkassky@gmail.com>,
        "pgsql-performance@lists.postgresql.org"
 <pgsql-performance@lists.postgresql.org>
Subject: Re: database crash during pgbench run
In-reply-to: 
 <DM6PR12MB279649615CBE2BD6A85880C4ECA60@DM6PR12MB2796.namprd12.prod.outlook.com>
References: 
 <CA+t6e1=2kvj9Z0qsiF_cqUCpNDd_vc2PEBTex-oFDWVhNBArhw@mail.gmail.com>
 <28756.1544463896@sss.pgh.pa.us>
 <DM6PR12MB279649615CBE2BD6A85880C4ECA60@DM6PR12MB2796.namprd12.prod.outlook.com>
Comments: In-reply-to Greg Clough <Greg.Clough@ihsmarkit.com>
	message dated "Tue, 11 Dec 2018 14:35:20 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <10577.1544544074.1@sss.pgh.pa.us>
Date: Tue, 11 Dec 2018 11:01:14 -0500
Message-ID: <10578.1544544074@sss.pgh.pa.us>
Precedence: bulk

Greg Clough <Greg.Clough@ihsmarkit.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