| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: frogmouth failures |
| Date: | 2017-04-27 20:40:59 |
| Message-ID: | 20170427204059.m3uceqdxgwuml6oi@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-04-27 16:30:35 -0400, Tom Lane wrote:
> Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> > I've been trying to track down the cause of recent failures at the "make
> > check" stage on frogmouth, a 32-bit Windows/Mingw instance running on XP.
>
> I've been wondering about that too.
Same here. Over the years there've been a number of bug reports with
the same error code, so it's not necessarily specific to master. Could
just be a question of backend spawn rate or such.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-04-27 20:45:05 | Re: Unportable implementation of background worker start |
| Previous Message | Andrew Dunstan | 2017-04-27 20:40:07 | Re: frogmouth failures |