Re: BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown

From:	"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To:	<robertmhaas(at)gmail(dot)com>, yua ** <azuneko(at)hotmail(dot)com>
Cc:	<pgsql-bugs(at)postgresql(dot)org>
Subject:	Re: BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown
Date:	2010-01-19 15:37:14
Message-ID:	4B557D4C020000250002E758@gw.wicourts.gov
Views:	Raw Message | Whole Thread | Download mbox | Resend email
Thread:	2010-01-18 05:43:39 from "azuneko" <azuneko(at)hotmail(dot)com>  2010-01-18 20:33:02 from Robert Haas <robertmhaas(at)gmail(dot)com>   2010-01-19 10:26:10 from yua ゅぁ <azuneko(at)hotmail(dot)com>    2010-01-19 15:37:14 from "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>     2010-01-26 00:58:19 from yua ゅぁ <azuneko(at)hotmail(dot)com>      2010-01-26 14:55:10 from "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>      2010-01-26 23:38:05 from Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Lists:	pgsql-bugs

In response to

• Re: BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown at 2010-01-19 10:26:10 from yua ゅぁ

Responses

• Re: BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown at 2010-01-26 00:58:19 from yua ゅぁ

Browse pgsql-bugs by date

	From	Date	Subject
Next Message	WildWezyr	2010-01-19 17:07:45	BUG #5290: Simple loop with insert into and check to avoid duplicate values fails
Previous Message	WildWezyr	2010-01-19 11:07:24	BUG #5289: Unpredictable error in plpgsql function loop