Tom Lane a écrit :
Arnaud Lesauvage <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
