pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: mark@2ndquadrant.com, Thomas Munro <thomas.munro@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: stress test for parallel workers
Date: Fri, 11 Oct 2019 15:11:57 -0400
Message-ID: <15558.1570821117@sss.pgh.pa.us> (raw)
In-Reply-To: <ff2ef9aa-3af7-18e4-11bd-7481de2d4b47@2ndQuadrant.com>
References: <20190723162703.GM22387@telsasoft.com>
	<6762.1563902927@sss.pgh.pa.us>
	<20190723174222.GO22387@telsasoft.com>
	<CA+hUKGLch1bNWdG-G8YaeJbyVsper6hG86Ugx9tSWG3=a1R89Q@mail.gmail.com>
	<32179.1563919918@sss.pgh.pa.us>
	<CA+hUKGKZS32Lx1zViq0W8omCjHjBsN=dJZ8nX-rkhv1W=b802Q@mail.gmail.com>
	<17389.1563945314@sss.pgh.pa.us>
	<CA+hUKGL6cDyb2maq2P60cEsjFK=3saBCAj7sDzE3jysL-PRwqg@mail.gmail.com>
	<31032.1565152159@sss.pgh.pa.us>
	<CA+hUKGJNS6gZ=w=+wxjqhmck-voJ7FBuejHnw8mQgAp2yt0A9g@mail.gmail.com>
	<18537.1570421268@sss.pgh.pa.us>
	<5350.1570743291@sss.pgh.pa.us>
	<84813a30-8c34-9c32-7ad5-90d9eefba468@2ndQuadrant.com>
	<06d6be5a-7af2-ef78-0abc-6bfe500ead87@2ndQuadrant.com>
	<20032.1570808731@sss.pgh.pa.us>
	<ff2ef9aa-3af7-18e4-11bd-7481de2d4b47@2ndQuadrant.com>

Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> On 10/11/19 11:45 AM, Tom Lane wrote:
>> FWIW, I'm not excited about that as a permanent solution.  It requires
>> root privilege, and it affects the whole machine not only the buildfarm,
>> and making it persist across reboots is even more invasive.

> OK, but I'm not keen to have to tussle with coredumpctl. Right now our
> logic says: for every core file in the data directory try to get a
> backtrace. Use of systemd-coredump means that gets blown out of the
> water, and we no longer even have a simple test to see if our program
> caused a core dump.

I haven't played that much with this software, but it seems you can
do "coredumpctl list <path-to-executable>" to find out what it has
for a particular executable.  You would likely need a time-based
filter too (to avoid regurgitating previous runs' failures),
but that seems do-able.

			regards, tom lane





view thread (60+ messages)  latest in thread

Message-ID: <15558.1570821117@sss.pgh.pa.us>
Permalink:  ../15558.1570821117@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15558.1570821117@sss.pgh.pa.us

 · 

reply
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, andrew.dunstan@2ndquadrant.com, thomas.munro@gmail.com, pryzby@telsasoft.com, andres@anarazel.de
  Subject: Re: stress test for parallel workers
  In-Reply-To: <15558.1570821117@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