| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dave Page <dave(dot)page(at)enterprisedb(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, CM Team <cm(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, bernd(dot)helmle(at)credativ(dot)de |
| Subject: | Re: test_shm_mq failing on anole (was: Sending out a request for more buildfarm animals?) |
| Date: | 2014-05-09 14:18:24 |
| Message-ID: | CA+Tgmoa2q9GSVsPn46b9-4pmv6cE_P5K7+aQFs+qT=LJ_vjhYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 3, 2014 at 4:31 AM, Dave Page <dave(dot)page(at)enterprisedb(dot)com> wrote:
> Hamid(at)EDB; Can you please have someone configure anole to build git
> head as well as the other branches? Thanks.
The test_shm_mq regression tests hung on this machine this morning.
Hamid was able to give me access to log in and troubleshoot.
Unfortunately, I wasn't able to completely track down the problem
before accidentally killing off the running cluster, but it looks like
test_shm_mq_pipelined() tried to start 3 background workers and the
postmaster only ever launched one of them, so the test just sat there
and waited for the other two workers to start. At this point, I have
no idea what could cause the postmaster to be asleep at the switch
like this, but it seems clear that's what happened.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2014-05-09 14:19:32 | Re: Archive recovery won't be completed on some situation. |
| Previous Message | Tom Lane | 2014-05-09 14:07:10 | Re: Cache lookup error when using jsonb, json_build_object and a WITH clause |