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

From: yua ゅぁ <azuneko(at)hotmail(dot)com>
To: <kevin(dot)grittner(at)wicourts(dot)gov>, <robertmhaas(at)gmail(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-26 00:58:19
Message-ID: KAW101-W22B60468F76175CB5A9DDBAE5E0@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Hello,

Kevin.

Thank you good guidelines.

guidelines questions.

Q1 postgres Version

A1 PostgreSQL 8.3.3 on i386-portbld-freebsd7.0, compiled by GCC cc (GCC)
4.2.1 20070719 [FreeBSD]

ports Install.

Q2
A2 x

Q3 Query
A3 x

Q4 Query
A4 x

Q5 Error Message
A5
postgres[681]: [506-1] WARNING: worker took too long to start; cancelled Nov 12 11:15:12 kddi-nwmgr01 postgres[681]:
[507-1] WARNING: worker took too long to start; cancelled

ps -auxeww
---------+---------+---------+---------+---------+---------+--------
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
pgsql 682 99.0 0.1 9336 2740 ?? Rs 27Nov08 343573:19.27 USER=pgsql

Q6 PostgreSQL Programs
A6 php5-pdo_pgsql-5.2.12
p5-DBD-Pg-2.16.0

Q8 OS Version
A8 FreeBSD 7.0-RELEASE-p2

Q9 Hardware Info
A9
CPU : Intel, Xeon2.4
RAM : 2GB
Storage
RAID Card : LSI MegaRAID
Battery Cache : YES
write-back Cache : NO
Software RAID : NO ( Hardware RAID)
SAN : NO
Disk : 7,200rpm SATA 3lot
Disk : RAID5 3slot

> Date: Tue, 19 Jan 2010 09:37:14 -0600
> From: Kevin(dot)Grittner(at)wicourts(dot)gov
> To: robertmhaas(at)gmail(dot)com; azuneko(at)hotmail(dot)com
> CC: pgsql-bugs(at)postgresql(dot)org
> Subject: Re: [BUGS] BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown
>
> 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

_________________________________________________________________
【節約!】インターネット代、見直しませんか?
http://campaign.live.jp/eaccess/Top/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mark Kazemier 2010-01-26 13:21:05 Foreign key constaint can be broken
Previous Message Milen A. Radev 2010-01-25 19:49:02 Re: BUG #5290: Simple loop with insert into and check to avoid duplicate values fails