From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org, Thomas Munro <thomas.munro@enterprisedb.com>
Subject: Re: stress test for parallel workers
Date: Tue, 23 Jul 2019 13:28:47 -0400
Message-ID: <6762.1563902927@sss.pgh.pa.us> (raw)
In-Reply-To: <20190723162703.GM22387@telsasoft.com>
References: <20190723162703.GM22387@telsasoft.com>
Justin Pryzby <pryzby@telsasoft.com> writes:
> Does anyone have a stress test for parallel workers ?
> On a customer's new VM, I got this several times while (trying to) migrate their DB:
> < 2019-07-23 10:33:51.552 CDT postgres >FATAL: postmaster exited during a parallel transaction
We've been seeing this irregularly in the buildfarm, too. I've been
suspicious that it's from an OOM kill on the postmaster in the
buildfarm cases, but ...
> There's nothing in dmesg nor in postgres logs.
... you'd think an OOM kill would show up in the kernel log.
(Not necessarily in dmesg, though. Did you try syslog?)
> Ideally a minimal test, since I'm apparently going to
> have to run under gdb to see how it's dying, or even what process is failing.
Like it told you, it's the postmaster that's going away.
That's Not Supposed To Happen, of course, but unfortunately Linux'
OOM kill heuristic preferentially targets the postmaster when
its children are consuming too many resources.
If that is the problem, there's some info on working around it at
https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT
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-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pryzby@telsasoft.com, thomas.munro@enterprisedb.com
Subject: Re: stress test for parallel workers
In-Reply-To: <6762.1563902927@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