Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id E8BB89F9F8E for ; Tue, 21 Aug 2007 19:05:11 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 09512-01 for ; Tue, 21 Aug 2007 19:05:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from corp.etelos.com (corp.etelos.com [216.251.101.81]) by postgresql.org (Postfix) with ESMTP id 3FFA59F9F9E for ; Tue, 21 Aug 2007 19:05:07 -0300 (ADT) Received: from [192.168.4.109] (unknown [216.251.108.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by corp.etelos.com (Postfix) with ESMTP id 98A1BFAC9B; Tue, 21 Aug 2007 15:05:03 -0700 (PDT) Message-ID: <46CB618B.1010901@etelos.com> Date: Tue, 21 Aug 2007 15:04:59 -0700 From: Jon Collette User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: =?UTF-8?B?Um9kcmlnbyBEZSBMZcOzbg==?= CC: pgsql-sql@postgresql.org Subject: Re: Make a SQL statement not run trigger References: <46CB5876.80003@etelos.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/175 X-Sequence-Number: 29113 Thanks for the reply. It looks like this will disable the trigger for all connections to the database. So if the chance occured that another connection was using the table at the same time it wouldn't launch the trigger either? am I wrong? I hope so ;) Rodrigo De León wrote: > On 8/21/07, Jon Collette wrote: > >> Is it possible to run an insert,update, or delete and have it not launch >> a trigger like it normally would? >> > > alter table disable trigger ... > > http://www.postgresql.org/docs/8.2/static/sql-altertable.html > > ---------------------------(end of broadcast)--------------------------- > TIP 7: You can help support the PostgreSQL project by donating at > > http://www.postgresql.org/about/donate >