Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-bugs
yua **<azuneko(at)hotmail(dot)com> wrote:
 
> What kind of information shall, I geve you
 
There are some good guidelines here:
 
http://wiki.postgresql.org/wiki/SlowQueryQuestions
 
-Kevin

In response to

Responses

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group