Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e6O65Ih25217 for ; Mon, 24 Jul 2000 02:05:18 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id CAA23365; Mon, 24 Jul 2000 02:04:57 -0400 (EDT) To: "Robert B. Easter" cc: pgsql-general@postgresql.org Subject: Re: Is there any way to speed up PL/TCL functions? In-reply-to: <00072401305903.00253@comptechnews> References: <00072401305903.00253@comptechnews> Comments: In-reply-to "Robert B. Easter" message dated "Mon, 24 Jul 2000 01:15:00 -0400" Date: Mon, 24 Jul 2000 02:04:57 -0400 Message-ID: <23362.964418697@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/834 "Robert B. Easter" writes: > I'm using some PL/TCL functions and triggers to do some special > inserts. When I do an insert that uses these procedures, I get the > "INSERT xxxxxx 1" response back immediately, but then there is a pause > before the next query is executed. It appears as if the PL/TCL runs > fast but after its finished it has to spend a significant amount of > time cleaning up before the next query can run. That doesn't make any sense as stated, but it might be that your triggers are "deferred" (execute-at-commit). I believe the INSERT command response gets sent before transaction commit, so what's probably really happening is just that your trigger is slow. > Is this the way it is? Any way to reduce this pause? Hard to say without knowing what your trigger is doing. regards, tom lane