Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E287765007C for ; Mon, 14 Jul 2008 03:52:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 34781-09 for ; Mon, 14 Jul 2008 03:52:38 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by postgresql.org (Postfix) with ESMTP id 7F353650054 for ; Mon, 14 Jul 2008 03:52:40 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so5771405rvf.43 for ; Sun, 13 Jul 2008 23:52:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Jr2BbMNR4w5f3nRpayjpnv5r6oCll5CknmgMkW4FnUk=; b=WHoZk4mnitAVbwx5db4J56O2ekT/hvMSzcUU9RBC7lCt5qPHvkKcg7842dLi4UjnKZ a9CF8iDTb3x/Nic3SEGUYM3YhlWzJtlg0O97fCyWZ219y8+Tkl6yBMT+izp9HJy3bIqk MI8WM+WkGDZtR5PuJtBfJzWjyyxkEzY1CO2Ww= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=RLQoldkGHfhCfgrEXrgc99XRW4KKaE+mWKXohJKKw600CU2xUg+amKbsDTfIZINrzj ljJWOoIcsu7pFvKYh/ch2hep75szVmRKRdiZdyy6M+A8Hed28man23n+S1UEPxDKKo+u xIDVs97ehTenQlX51qD0lMhodHJtBo5Mw8Wo8= Received: by 10.140.249.20 with SMTP id w20mr6388427rvh.21.1216018358843; Sun, 13 Jul 2008 23:52:38 -0700 (PDT) Received: from ?10.1.1.5? ( [203.206.174.100]) by mx.google.com with ESMTPS id f21sm7740012rvb.0.2008.07.13.23.52.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 13 Jul 2008 23:52:35 -0700 (PDT) Message-ID: <487AF7AE.6020606@gmail.com> Date: Mon, 14 Jul 2008 16:52:30 +1000 From: Chris User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Praveen CC: pgsql-performance@postgresql.org Subject: Re: Trigger is not firing immediately References: <001001c8e57b$b72dcf70$274610ac@praveenkm> In-Reply-To: <001001c8e57b$b72dcf70$274610ac@praveenkm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/123 X-Sequence-Number: 30723 Praveen wrote: > > Hi All, > I am having a trigger in table, If I update the the table manually > trigger is firing immediately(say 200ms per row), But if I update the > table through procedure the trigger is taking time to fire(say 7 to 10 > seconds per row). > > Please tell me what kind of changes can I make so that trigger fire > immediately while updating the table through procedure ? Sending the same email over and over again isn't going to get you a response any quicker. If you send the details of the trigger and the tables/fields it affects then you might get a more helpful response. -- Postgresql & php tutorials http://www.designmagick.com/