| From: | Arnaud Lesauvage <thewild(at)freesurf(dot)fr> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | Ragnar <gnari(at)hive(dot)is>, Jens Schipkowski <jens(dot)schipkowski(at)apus(dot)co(dot)at>, pgsql-performance(at)postgresql(dot)org | 
| Subject: | Re: Slow update with simple query | 
| Date: | 2006-12-14 15:23:00 | 
| Message-ID: | 45816C54.5010602@freesurf.fr | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-performance | 
Tom Lane a écrit :
> Arnaud Lesauvage <thewild(at)freesurf(dot)fr> writes:
>> I must be missing something, so here is the full table description.
> 
> It looks pretty harmless, except for
> 
>> CREATE TRIGGER parse_log_trigger
>>     BEFORE INSERT
>>     ON statistiques.log
>>     FOR EACH ROW
>>     EXECUTE PROCEDURE statistiques.parse_log_trigger();
> 
> It seems the time must be going into this trigger function.  What
> does it do?
A lot of things ! Indeed, if it runs it will very badly hurt performances (table 
lookups, string manipulation, etc...) !
But it should only be tringered on INSERTs, and I am doing an UPDATE !
I can post the function's body if you want.
Regards
--
Arnaud
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2006-12-14 15:24:12 | Re: New to PostgreSQL, performance considerations | 
| Previous Message | Tom Lane | 2006-12-14 15:18:14 | Re: Slow update with simple query |