I am using triggers for all the events (insert,delete,update) please
find the details below.

trg_delpointtable BEFORE DELETE ON pointtable FOR EACH ROW EXECUTE
PROCEDURE pp_delpointtable()

trg_insdelpoints AFTER DELETE ON pointtable FOR EACH ROW EXECUTE
PROCEDURE pp_insdelpoints()

trgins_pointtable AFTER INSERT ON pointtable FOR EACH ROW EXECUTE
PROCEDURE pp_inspointtable()

trupd_pointtable AFTER UPDATE ON pointtable FOR EACH ROW EXECUTE
PROCEDURE pp_updpointtable()


Basically, this each trigger modifies the content of other dependent
tables.

Best Regards,
Jeeva.K

-----Original Message-----
From: Tino Wildenhain [mailto:tino@wildenhain.de]
Sent: Tuesday, February 28, 2006 10:34 AM
To: Jeevanandam, Kathirvel (IE10)
Cc: pgsql-general@postgresql.org
Subject: triggers, performance Was: Re: [GENERAL] rotate records

Jeevanandam, Kathirvel (IE10) schrieb:
> Hi all,
>
> I am facing performance issues even with less than 3000 records, I am
> using Triggers/SPs in all the tables. What could be the problem.
> Any idea it is good to use triggers w.r.t performance?

Much to general. What triggers? (what are they doing, when are
they invoked...?). Please provide much greater details with
your request or nobody can help.

Regards
Tino

PS: and try not to steal threads

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

And what do those functions do? And do their options trigger other
triggers? How about an EXPLAIN ANALYZE from a problem query, too.

On Tue, Feb 28, 2006 at 11:24:34AM +0530, Jeevanandam, Kathirvel (IE10) wrote:
> I am using triggers for all the events (insert,delete,update) please
> find the details below.
>
> trg_delpointtable BEFORE DELETE ON pointtable FOR EACH ROW EXECUTE
> PROCEDURE pp_delpointtable()
>
> trg_insdelpoints AFTER DELETE ON pointtable FOR EACH ROW EXECUTE
> PROCEDURE pp_insdelpoints()
>
> trgins_pointtable AFTER INSERT ON pointtable FOR EACH ROW EXECUTE
> PROCEDURE pp_inspointtable()
>
> trupd_pointtable AFTER UPDATE ON pointtable FOR EACH ROW EXECUTE
> PROCEDURE pp_updpointtable()
>
>
> Basically, this each trigger modifies the content of other dependent
> tables.
>
> Best Regards,
> Jeeva.K
>
> -----Original Message-----
> From: Tino Wildenhain [mailto:tino@wildenhain.de]
> Sent: Tuesday, February 28, 2006 10:34 AM
> To: Jeevanandam, Kathirvel (IE10)
> Cc: pgsql-general@postgresql.org
> Subject: triggers, performance Was: Re: [GENERAL] rotate records
>
> Jeevanandam, Kathirvel (IE10) schrieb:
> > Hi all,
> >
> > I am facing performance issues even with less than 3000 records, I am
> > using Triggers/SPs in all the tables. What could be the problem.
> > Any idea it is good to use triggers w.r.t performance?
>
> Much to general. What triggers? (what are they doing, when are
> they invoked...?). Please provide much greater details with
> your request or nobody can help.
>
> Regards
> Tino
>
> PS: and try not to steal threads
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq