Received: from www1.translationforge.com (unknown [212.11.36.58]) by postgresql.org (Postfix) with ESMTP id 7904E4758EE for ; Sat, 20 Apr 2002 03:08:28 -0400 (EDT) Received: from linus.translationforge.com ([192.168.1.102]) by www1.translationforge.com (8.12.1/8.12.1) with ESMTP id g3K77htb012405; Sat, 20 Apr 2002 09:08:24 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Jean-Michel POURE Reply-To: jmpoure@translationforge.com Organization: Translationforge To: , Subject: Re: PERFORMANCE Date: Sat, 20 Apr 2002 09:07:41 +0200 X-Mailer: KMail [version 1.4] References: <1463.192.168.1.205.1019057195.squirrel@www.saolucas-se.com.br> In-Reply-To: <1463.192.168.1.205.1019057195.squirrel@www.saolucas-se.com.br> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200204200907.41783.jmpoure@translationforge.com> X-Archive-Number: 200204/70 X-Sequence-Number: 1094 > "IS THERE ANYONE THAT CANT GIVE US SOME HOPE TO PERSIST ON POSTGRES OR IS > THIS A LOST BATLE?" I figured out the only way to "crash" PostgreSQL was entering an endless lo= op.=20 This happened to me sereval times (a trigger was spreading to another trigg= er,=20 which in turned called back the first trigger; or simply an endless loop in= a=20 PLpgSQL function). When entering an endless loop, PostgreSQL activity climb= s=20 up, untill it reaches 100% user activity and dramaticaly slows down Linux.= =20 Isn't what happens to you? Turn on debuging to notice where the endless loo= p=20 happens. This will be probably fixed in the future with an "endless loop protection"= =20 feature. Feel free to give us your feedback as soon as you discovers what is going o= n. Cheers, Jean-Michel