Re: stress test for parallel workers - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: stress test for parallel workers
Date
Msg-id ff2ef9aa-3af7-18e4-11bd-7481de2d4b47@2ndQuadrant.com
Whole thread Raw
In response to Re: stress test for parallel workers  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: stress test for parallel workers
List pgsql-hackers
On 10/11/19 11:45 AM, Tom Lane wrote:
> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>>> At least on F29 I have set /proc/sys/kernel/core_pattern and it works.
> 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.


cheers


andrew


-- 

Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: v12.0: ERROR: could not find pathkey item to sort
Next
From: Andrew Dunstan
Date:
Subject: Re: Connect as multiple users using single client certificate