From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Clough <Greg.Clough@ihsmarkit.com>
Cc: Mariel Cherkassky <mariel.cherkassky@gmail.com>
Cc: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: Re: database crash during pgbench run
Date: Tue, 11 Dec 2018 11:01:14 -0500
Message-ID: <10578.1544544074@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, Greg.Clough@ihsmarkit.com, mariel.cherkassky@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: database crash during pgbench run
In-Reply-To: <10578.1544544074@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox