| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | Postgresql Hackers Mailinglist <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: spoonbill vs. -HEAD |
| Date: | 2013-03-26 19:45:49 |
| Message-ID: | 18421.1364327149@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> I finally started to investigate why spoonbill stopped reporting to the
> buildfarm feedback about 2 months ago.
> It seems that the foreign-keys locking patch (or something commity very
> close to January 23th) broke it in a fairly annoying way - running the
> buildfarm script seems to
> consistently "stall" during the isolationtester part of the regression
> testing leaving the postgresql instance running causing all future
> buildfarm runs to fail...
It looks from here like the isolationtester client is what's dropping
the ball --- the backend states are unsurprising, and two of them are
waiting for a new client command. Can you get a stack trace from the
isolationtester process?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-03-26 19:47:18 | Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL) |
| Previous Message | Robert Haas | 2013-03-26 19:41:09 | Re: sql_drop Event Triggerg |