Horton

Re: stress test for parallel workers

Heikki Linnakangas <hlinnaka@iki.fi>

View thread View on postgr.es
From: Heikki Linnakangas <hlinnaka@iki.fi>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-08-07T16:08:04Z
Lists: pgsql-hackers 
On 07/08/2019 17:45, Tom Lane wrote:
> Heikki Linnakangas <hlinnaka@iki.fi> writes:
>> On 07/08/2019 16:57, Tom Lane wrote:
>>> Also, if you're using systemd or something else that thinks it
>>> ought to interfere with where cores get dropped, that could be
>>> a problem.
> 
>> I think they should just go to a file called "core", I don't think I've
>> changed any settings related to it, at least. I tried "find / -name
>> core*", but didn't find any core files, though.
> 
> On Linux machines the first thing to check is
> 
> cat /proc/sys/kernel/core_pattern
> 
> On a Debian machine I have handy, that just says "core", but Red Hat
> tends to mess with it ...

It's just "core" on chipmunk, too.

- Heikki

Commits

  1. In the postmaster, rely on the signal infrastructure to block signals.

  2. Paper over regression failures in infinite_recurse() on PPC64 Linux.

  3. Hack pg_ctl to report postmaster's exit status.

  4. Re-order some regression test scripts for more parallelism.