On 03/26/2013 08:45 PM, Tom Lane wrote: > Stefan Kaltenbrunner <ste...@kaltenbrunner.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?
https://www.kaltenbrunner.cc/files/isolationtester.txt Stefan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
