[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-performance
Subject:    Re: database crash during pgbench run
From:       Merlin Moncure <mmoncure () gmail ! com>
Date:       2018-12-21 13:40:25
Message-ID: CAHyXU0xj0Bhm1fM-w=hkjefHmKbD4jrtriWUaQomQvx_+w_gJw () mail ! gmail ! com
[Download RAW message or body]

On Tue, Dec 11, 2018 at 10:01 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> 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.

Yeah.  To add to this, pgbench runs are extremely unlikely to cause
the kind of memory consumption issues that would trigger an OOM.  This
is definitely not a database crash, just some kind of administrative
problem.  Some things that might be helpful to help figure this out:
*) What o/s
*) how was the database installed
*) how exactly did the database start
*) are we looking at something exotic here (cloud managed postgres,
exotic storage, etc)

merlin

[prev in list] [next in list] [prev in thread] [next in thread]