| From: | Jean-Michel POURE <jmpoure(at)translationforge(dot)com> |
|---|---|
| To: | <valeria(at)saolucas-se(dot)com(dot)br>, <pgsql-php(at)postgresql(dot)org> |
| Subject: | Re: PERFORMANCE |
| Date: | 2002-04-20 07:07:41 |
| Message-ID: | 200204200907.41783.jmpoure@translationforge.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-php |
> "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 loop.
This happened to me sereval times (a trigger was spreading to another trigger,
which in turned called back the first trigger; or simply an endless loop in a
PLpgSQL function). When entering an endless loop, PostgreSQL activity climbs
up, untill it reaches 100% user activity and dramaticaly slows down Linux.
Isn't what happens to you? Turn on debuging to notice where the endless loop
happens.
This will be probably fixed in the future with an "endless loop protection"
feature.
Feel free to give us your feedback as soon as you discovers what is going on.
Cheers,
Jean-Michel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel POURE | 2002-04-20 07:16:28 | Re: PERFORMANCE |
| Previous Message | Dave | 2002-04-19 17:45:15 | Re: Security - local(TRUST) and php/perl access |