pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Papp, Gyozo <pgerzson@freestart.hu>
To: jmpoure@translationforge.com
To: valeria@saolucas-se.com.br
To: pgsql-php@postgresql.org
Subject: Re: PERFORMANCE
Date: Sat, 20 Apr 2002 10:49:38 +0200
Message-ID: <008301c1e848$4e5b9a40$01fdfea9@jaguar> (raw)
References: <1463.192.168.1.205.1019057195.squirrel@www.saolucas-se.com.br>
	<200204181017.56709.jmpoure@translationforge.com>
	<011901c1e6b6$e990c5a0$01fdfea9@jaguar>
	<200204200916.28425.jmpoure@translationforge.com>

Hi,

Paulo wrote:

| I´m new on the list and I´ve been using postgres on a production 
| environment for 3 months.  My team and I have developed a system for a
| Hospital in which we work with php-postgres-linux.  In the begining 
| everything was fine.  As soon as the tables grew larger, we´ve begun to
| experience an enormous performance fall.  By now, the system is

and Jean-Michel wrote:
| 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.

Yes, Jean-Michel is right, please try to debug what queries sent to the backend.
BTW, I'm doubt that it would be an endless loop rather than mis configured or
misconcepted (if you understand what I mean) database design.
Paulo stated there were times when everything was fine, pg just recently slowed
down. It might be a very evil trigger which starts to misbehave as tables grow.
BTW, it could be, really. If that trigger works too slowly...







view thread (13+ messages)  latest in thread

Message-ID: <008301c1e848$4e5b9a40$01fdfea9@jaguar>
Permalink:  ../008301c1e848$4e5b9a40$01fdfea9@jaguar/
Also on:    postgresql.org/message-id/008301c1e848$4e5b9a40$01fdfea9@jaguar

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: pgerzson@freestart.hu, jmpoure@translationforge.com, valeria@saolucas-se.com.br
  Subject: Re: PERFORMANCE
  In-Reply-To: <008301c1e848$4e5b9a40$01fdfea9@jaguar>
  References: <1463.192.168.1.205.1019057195.squirrel@www.saolucas-se.com.br> <200204181017.56709.jmpoure@translationforge.com> <011901c1e6b6$e990c5a0$01fdfea9@jaguar> <200204200916.28425.jmpoure@translationforge.com> <008301c1e848$4e5b9a40$01fdfea9@jaguar>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox