DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=VIl40L+AC7lUOaLod8vkyCC66h7D8P9Te3MDl1xiNojZ48F9dgVR+iawXgZxj0SB+5nLHwIcgOMYQnsTq74ygWynbleUf8ZmIy9r/jPYHQBvhGslQ+ojye/6scuJ5PFAIRkkqr2KPSaMZvZ6vR7NaK157bykIWWU/ei6znDjXzc=
Message-ID: <dcc563d10708211507r351a46efxc758168f6032ab3f@mail.gmail.com>
Date: Tue, 21 Aug 2007 17:07:29 -0500
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Jon Collette" <jon@etelos.com>
Subject: Re: Make a SQL statement not run trigger
Cc: pgsql-sql@postgresql.org
In-Reply-To: <46CB5876.80003@etelos.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46CB5876.80003@etelos.com>

On 8/21/07, Jon Collette <jon@etelos.com> wrote:
> Is it possible to run an insert,update, or delete and have it not launch
> a trigger like it normally would?
>
> For example could I set a value
> DONOTRUN = True;
> insert into contacts ....

The closest thing to a session variable for pgsql is going to likely
be a temp table.  you could have a temp table for each session that
stores such things and the trigger looks in the temp table to see what
to do.

> Or is there just a global variable I could set to disable triggers and
> then reset it? And would that be a per connection variable?

Yes, but that would open you up to race conditions.  If another
session wanted the trigger to fire it would not get it.  Using a temp
table would allow you to get around the race condition.