| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | Postgresql Hackers Mailinglist <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | spoonbill vs. -HEAD |
| Date: | 2013-03-26 18:50:05 |
| Message-ID: | 5151EDDD.9080004@kaltenbrunner.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all!
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...
The process listing at that time looks like:
https://www.kaltenbrunner.cc/files/process_listing.txt
pg_stats_activity of the running instance:
https://www.kaltenbrunner.cc/files/pg_stat_activity.txt
pg_locks:
https://www.kaltenbrunner.cc/files/pg_locks.txt
backtraces of the three backends:
https://www.kaltenbrunner.cc/files/bt_20467.txt
https://www.kaltenbrunner.cc/files/bt_20897.txt
https://www.kaltenbrunner.cc/files/bt_24285.txt
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-03-26 19:02:24 | Re: sql_drop Event Triggerg |
| Previous Message | Gavin Flower | 2013-03-26 18:49:14 | Re: adding support for zero-attribute unique/etc keys |