| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: stress test for parallel workers |
| Date: | 2019-08-07 13:30:46 |
| Message-ID: | 953ce625-74b1-cfcc-3814-0b0f6e189bc0@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/08/2019 02:57, Thomas Munro wrote:
> On Wed, Jul 24, 2019 at 5:15 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So I think I've got to take back the assertion that we've got
>> some lurking generic problem. This pattern looks way more
>> like a platform-specific issue. Overaggressive OOM killer
>> would fit the facts on vulpes/wobbegong, perhaps, though
>> it's odd that it only happens on HEAD runs.
>
> chipmunk also:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=chipmunk&dt=2019-08-06%2014:16:16
>
> I wondered if the build farm should try to report OOM kill -9 or other
> signal activity affecting the postmaster.
FWIW, I looked at the logs in /var/log/* on chipmunk, and found no
evidence of OOM killings. I can see nothing unusual in the OS logs
around the time of that failure.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Igrishin | 2019-08-07 13:37:58 | Re: Small patch to fix build on Windows |
| Previous Message | Michael Paquier | 2019-08-07 13:24:22 | Regression test failure in regression test temp.sql |